We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
API improvement
To support SQL statement like:
SELECT 1 LIMIT 1::bigint
This is how postgres send limit clause to remote server when the original query contains a limit clause. Currently we got an error say:
ERROR: Failed to plan SQL: Error during planning: Unexpected expression in LIMIT clause
No response
The text was updated successfully, but these errors were encountered:
This issue has been fixed in datafusion 43 apache/datafusion#13028
Sorry, something went wrong.
feat: add a temporary sql rewrite for cast in limit
3793d1b
this issue is described in GreptimeTeam#5097
feat: add cursor statements (#5094)
3133f3f
* 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
No branches or pull requests
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: