-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
[Native] Add debug config for native engine execution #21036
Conversation
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.
Thans @bikramSingh91 for adding the configs. Looks good to me.
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.
@bikramSingh91 Thanks.
Please, update commit message to return the following redundant text.
Test Plan:
Updated and added unit tests
@@ -31,16 +31,31 @@ TEST_F(QueryContextManagerTest, nativeSessionProperties) { | |||
.systemProperties = { | |||
{"native_max_spill_level", "1"}, | |||
{"native_spill_compression_codec", "NONE"}, | |||
{"native_join_spill_enabled", "true"}, |
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.
Should we move this change to another PR?
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.
This part is just expanding the unit testing and not changing any defaults so is fairly benign to keep in this PR. Please let me know if you still feel strongly about separating this.
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.
This is fine. Thanks for clarifying!
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.
@bikramSingh91 can the Velox advance be moved to another PR?
@majetideepak Please take a look #21039 |
@bikramSingh91 can you rebase with master and remove the advance Velox bits? |
This patch adds the required changes to allow setting a debug query config specific to native engine. The query config added on presto side is `native_debug.validate_output_from_operators` Test Plan: Updated and added unit tests
045aefc
to
b358641
Compare
@majetideepak Updated the PR and all tests pass, can you please proceed with the merge |
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.
Thanks!
This patch adds the required changes to allow setting a debug query config
specific to native engine. The query config added on presto side is
native_debug.validate_output_from_operators
Depends on: #21039 to pull in latest changes from velox