-
Notifications
You must be signed in to change notification settings - Fork 15
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
Fix issues with queries that are bigger than 2GB #266
Conversation
There are changes done to the BigByteArrayInputStream, that might not be necessary anymore. Should I revert them? |
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.
Thx for the PR. Looks good to me. I just commented some minor issues below.
Please also provide benchmarks comparing this with develop as a baseline to make sure we don't introduce a performance regression here. Please use the GraalVM binaries.
docs/configuration/big_queries.md
Outdated
# Reading Large Queries | ||
|
||
When working with large queries (Queries that are larger than 2^31 Bytes or ~2GB), |
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.
# Reading Large Queries | |
When working with large queries (Queries that are larger than 2^31 Bytes or ~2GB), | |
# Huge Query Strings | |
When working with large query strings (longer than 2³² Bytes or ~2GB), |
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.
I moved the section to the file queries.md
.
No description provided.