-
Notifications
You must be signed in to change notification settings - Fork 322
feat: eliminate performance sensitive #877
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
feat: eliminate performance sensitive #877
Conversation
1. eliminate set performance sensitive = true|false in cli 2. remove related API in C++ sdk and java sdk 3. add enable_request_performance_sensitive in engine option, for ddl gen to get a request physical plan performance-insensitive 4. fix yaml case, online batch queries can be executed performance insensitive
…minate_performance_sensitive # Conflicts: # hybridse/include/vm/physical_op.h # hybridse/src/vm/physical_op.cc # hybridse/src/vm/transform.cc # hybridse/src/vm/transform_test.cc
Codecov Report
@@ Coverage Diff @@
## main #877 +/- ##
============================================
+ Coverage 42.36% 42.40% +0.03%
Complexity 219 219
============================================
Files 572 572
Lines 105529 105600 +71
Branches 946 946
============================================
+ Hits 44703 44775 +72
+ Misses 60682 60681 -1
Partials 144 144
Continue to review full report at Codecov.
|
remember to update the related docs |
DONE |
…at/eliminate_performance_sensitive
…minate_performance_sensitive # Conflicts: # src/cmd/file_option_parser.h
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.
LGTM
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.
LGTM
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
feature
What is the current behaviour? (You can also link to an open issue here)
resolve Eliminate the concept of performance-sensitive mode for users #796
What is the new behaviour (if this is a feature change)?
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information: