refactor: use closure-based result iteration#363
Merged
Conversation
KKould
force-pushed
the
result-tuple-visitor-tpcc
branch
from
aff8b6e to
006333c
Compare
KKould
force-pushed
the
result-tuple-visitor-tpcc
branch
from
006333c to
dac3259
Compare
KKould
changed the title
* Use space-saving counters for column TopN * Fallback on high-error TopN estimates * refactor(optimizer): remove unused ColumnTopN merge API
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
next_tupleAPI so callers can consume the executor tuple slot without the old owned-iterator pathkite_sql 0.3.3/kite_sql_serde_macros 0.2.3Validation
cargo fmt --checkcargo metadata --format-version 1 --no-depsgit diff --check --cachedcargo test -p tpccmake test-all