-
Notifications
You must be signed in to change notification settings - Fork 2.5k
[CALCITE-7592] Add expression support for FETCH #5004
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
Open
tkalkirill
wants to merge
8
commits into
apache:main
Choose a base branch
from
tkalkirill:calcite-7592
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
68aadce
[CALCITE-759] Wip
tkalkirill 143b9b6
[CALCITE-7592] Wip
tkalkirill f03a3b9
[CALCITE-7592] Wip
tkalkirill 8bba1aa
[CALCITE-7592] Wip
tkalkirill 139fdc3
[CALCITE-7592] Wip
tkalkirill c499982
[CALCITE-7592] Add Quidem test
tkalkirill e83ec8e
[CALCITE-7592] Add tests by review
tkalkirill 2739aa2
[CALCITE-7592] Little refactor for check dinamic parameters
tkalkirill File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
In Calcite, the LIMIT and OFFSET values are not restricted to the LONG type; they can be arbitrarily large. As this link, we will use BigDecimal. Is the restriction to the long type here due to issues with Enumerable execution? The
intabove has the same issue.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.
Yes, these bounds come from the execution APIs rather than from the logical FETCH representation. Enumerable and Bindable use int because ExtendedEnumerable.take accepts an int; Cassandra and Druid also expose integer limits. Elasticsearch and Geode use long. The logical Rex value and the generic reduction path remain BigDecimal, and MongoDB/JDBC do not apply these bounds. I can clarify this in the Javadocs.
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.
Thank you for your explanation. Although databases like PostgreSQL use the bigint type, Calcite has fully converged to the bigdecimal type. I don't think we should impose restrictions on Calcite's EnumerableLimit. If other databases require their own restrictions, they can implement them in their respective systems. This type was agreed upon with Julian et al.