-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Consider adding "insert_or_overwrite" call to DB #7
Labels
Comments
aditya-travis
added a commit
to aditya-travis/YCSB
that referenced
this issue
Mar 22, 2016
hse-project
referenced
this issue
in hse-project/hse-ycsb
Apr 17, 2020
…0.17.0-LargeRecordCount * commit '6f59619d38622ec3a1447ce1292b193a4800b9ae': Streamlines the hse ycsb property list.
zyguan
pushed a commit
to zyguan/ycsb
that referenced
this issue
Sep 21, 2020
Adding a binding for YSQL with 2 keys to accomodate the scan scenario…
jyemin
pushed a commit
to jyemin/YCSB
that referenced
this issue
Apr 13, 2021
Allow for generation of compressible data of varying compressibility
xinlian12
pushed a commit
to xinlian12/YCSB
that referenced
this issue
Jul 26, 2023
…eCosmosSDKTo4.34.0 Updating cosmos sdk to latest 4.34.0
smkniazi
added a commit
to smkniazi/YCSB
that referenced
this issue
Aug 7, 2023
RONDB-363 & RONDB-336
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Rusty suggested that some databases could optimize blind writes by logging the change without reading the old value. But to do so, you need to tell the database that the write is intended to obliterate any existing records with the same key. A new call is needed to do this.
The text was updated successfully, but these errors were encountered: