chore: enable query engine v2 by default #729
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As the final step to introduce the new planner #703, this PR reorganizes code structures, moves the legacy binder/planner/optimizer/executor to the
v1
module, and enables v2 by default. The legacy modules will be kept for a while, as a reference to improve the new one further. But it's not expected to add new features to it.Here is a rough statistic to compare the lines of code of the two versions:
* exclude unused executors
* use loc to count lines of code
Even taking into account the lack of test code in v2 for now, it is still much simpler than v1, using half of the code to achieve the same goal. Thanks to egg, we can make RisingLight lite again!