-
Notifications
You must be signed in to change notification settings - Fork 378
Failed to parse sql with expression in LIMIT clause #5097
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
Labels
C-enhancement
Category Enhancements
Comments
This issue has been fixed in datafusion 43 apache/datafusion#13028 |
sunng87
added a commit
to sunng87/greptimedb
that referenced
this issue
Dec 5, 2024
this issue is described in GreptimeTeam#5097
github-merge-queue bot
pushed a commit
that referenced
this issue
Dec 6, 2024
* feat: add sql parsers for cursor operations * feat: cursor operator * feat: implement RecordBatchStreamCursor * feat: implement cursor storage and execution * test: add tests * chore: update docstring * feat: add a temporary sql rewrite for cast in limit this issue is described in #5097 * test: add more sql for cursor integration test * feat: reject non-select query for cursor statement * refactor: address review issues * test: add empty result case * feat: address review comments
MichaelScofield
pushed a commit
that referenced
this issue
Jan 6, 2025
* feat: add sql parsers for cursor operations * feat: cursor operator * feat: implement RecordBatchStreamCursor * feat: implement cursor storage and execution * test: add tests * chore: update docstring * feat: add a temporary sql rewrite for cast in limit this issue is described in #5097 * test: add more sql for cursor integration test * feat: reject non-select query for cursor statement * refactor: address review issues * test: add empty result case * feat: address review comments
Fixed it already |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What type of enhancement is this?
API improvement
What does the enhancement do?
To support SQL statement like:
This is how postgres send limit clause to remote server when the original query contains a limit clause. Currently we got an error say:
Implementation challenges
No response
The text was updated successfully, but these errors were encountered: