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
[jdbc] added LIMIT to JDBC scan operation #468
Conversation
Now properly enforcing a scan of the given number of documents in the scan operation using the LIMIT modifier in the cached statement. Fixes brianfrankcooper#171.
I think to fulfill the intent of the scan operation there should be some ordering. Workload E (which uses scans) describes:
Allowing the DB to return, say, any record from the latter half of the database doesn't seem to match that intent. |
Also, from the original YCSB paper:
|
This will ensure record ordering my the primary key.
OK, added an ORDER BY clause to ensure record ordering by the primary key. |
Looks good to me. @cmccoy - Any other concerns. |
Looks good. Thanks! |
[jdbc] added LIMIT to JDBC scan operation
[jdbc] added LIMIT to JDBC scan operation
[jdbc] added LIMIT to JDBC scan operation
Now properly enforcing a scan of the given number of documents in the
scan operation using the LIMIT modifier in the cached statement.
Fixes #171.