-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make dwio::common::WriterOptions polymorphic #10380
Conversation
✅ Deploy Preview for meta-velox canceled.
|
This pull request was exported from Phabricator. Differential Revision: D59302873 |
This pull request was exported from Phabricator. Differential Revision: D59302873 |
1d37838
to
a4e6c23
Compare
Summary: Pull Request resolved: facebookincubator#10380 Making writer options a virtual class that could be specialized for different file formats to enable Velox users to provided them as part of a query plan. Today, there are a few different ways to pass writer parameters (serdeParams and hive config). They end up being serialized to strings, so can't be used with non-serializable configs. Moreover, file format specific configurations and code end-up in generic parts of the code, like HiveConnector. This will allow us to better organize file format specific options; for now only creating the framework to contain the changes. Reviewed By: kunalkataria, kparichay Differential Revision: D59302873
This pull request was exported from Phabricator. Differential Revision: D59302873 |
a4e6c23
to
8b4e5a1
Compare
Summary: Pull Request resolved: facebookincubator#10380 Making writer options a virtual class that could be specialized for different file formats to enable Velox users to provided them as part of a query plan. Today, there are a few different ways to pass writer parameters (serdeParams and hive config). They end up being serialized to strings, so can't be used with non-serializable configs. Moreover, file format specific configurations and code end-up in generic parts of the code, like HiveConnector. This will allow us to better organize file format specific options; for now only creating the framework to contain the changes. Reviewed By: kunalkataria, kparichay Differential Revision: D59302873
This pull request was exported from Phabricator. Differential Revision: D59302873 |
8b4e5a1
to
61fdaea
Compare
Summary: Pull Request resolved: facebookincubator#10380 Making writer options a virtual class that could be specialized for different file formats to enable Velox users to provided them as part of a query plan. Today, there are a few different ways to pass writer parameters (serdeParams and hive config). They end up being serialized to strings, so can't be used with non-serializable configs. Moreover, file format specific configurations and code end-up in generic parts of the code, like HiveConnector. This will allow us to better organize file format specific options; for now only creating the framework to contain the changes. Reviewed By: kunalkataria, kparichay Differential Revision: D59302873
This pull request was exported from Phabricator. Differential Revision: D59302873 |
Summary: Pull Request resolved: facebookincubator#10380 Making writer options a virtual class that could be specialized for different file formats to enable Velox users to provided them as part of a query plan. Today, there are a few different ways to pass writer parameters (serdeParams and hive config). They end up being serialized to strings, so can't be used with non-serializable configs. Moreover, file format specific configurations and code end-up in generic parts of the code, like HiveConnector. This will allow us to better organize file format specific options; for now only creating the framework to contain the changes. Reviewed By: kunalkataria, kparichay Differential Revision: D59302873
61fdaea
to
c572eb5
Compare
Summary: Pull Request resolved: facebookincubator#10380 Making writer options a virtual class that could be specialized for different file formats to enable Velox users to provided them as part of a query plan. Today, there are a few different ways to pass writer parameters (serdeParams and hive config). They end up being serialized to strings, so can't be used with non-serializable configs. Moreover, file format specific configurations and code end-up in generic parts of the code, like HiveConnector. This will allow us to better organize file format specific options; for now only creating the framework to contain the changes. Reviewed By: kunalkataria, kparichay Differential Revision: D59302873
c572eb5
to
d5c1282
Compare
This pull request was exported from Phabricator. Differential Revision: D59302873 |
Summary: Pull Request resolved: facebookincubator#10380 Making writer options a virtual class that could be specialized for different file formats to enable Velox users to provided them as part of a query plan. Today, there are a few different ways to pass writer parameters (serdeParams and hive config). They end up being serialized to strings, so can't be used with non-serializable configs. Moreover, file format specific configurations and code end-up in generic parts of the code, like HiveConnector. This will allow us to better organize file format specific options; for now only creating the framework to contain the changes. Reviewed By: kunalkataria, kparichay Differential Revision: D59302873
This pull request was exported from Phabricator. Differential Revision: D59302873 |
d5c1282
to
559b475
Compare
This pull request has been merged in e0680b9. |
Conbench analyzed the 1 benchmark run on commit There were no benchmark performance regressions. 🎉 The full Conbench report has more details. |
@@ -262,6 +267,7 @@ class HiveInsertTableHandle : public ConnectorInsertTableHandle { | |||
const std::shared_ptr<HiveBucketProperty> bucketProperty_; | |||
const std::optional<common::CompressionKind> compressionKind_; | |||
const std::unordered_map<std::string, std::string> serdeParameters_; | |||
const std::shared_ptr<dwio::common::WriterOptions> writerOptions_; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pedroerp Hi Pedro, I just bumped into this code.
WriterOptions
includes some contextual information (memory pool, spill config, etc.) so I guess it's the reason why it's not included in TableWriteNode's JSON serde, see code.
Do you think this is an issue? Given it's a special case that we include contextual information in query plan node.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Filed an issue: #12437
Summary:
Making writer options a virtual class that could be specialized for
different file formats to enable Velox users to provided them as part of a
query plan.
Today, there are a few different ways to pass writer parameters (serdeParams and
hive config). They end up being serialized to strings, so can't be used with
non-serializable configs. Moreover, file format specific configurations and code
end-up in generic parts of the code, like HiveConnector.
This will allow us to better organize file format specific options; for now only
creating the framework to contain the changes.
Differential Revision: D59302873