-
Notifications
You must be signed in to change notification settings - Fork 406
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
perf: conditional put for default log store (e.g. azure, gcs, minio, cloudflare) #2813
Conversation
a9738fd
to
b786513
Compare
4c6fa7f
to
2a190fc
Compare
158d09e
to
b818f8b
Compare
a7d5e2f
to
2ddfc6a
Compare
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.
This looks reasonable to me, I do have concerns just because we don't have great integration testing here between Rust/Spark (not a problem for this PR).
I think this change should require us to bump to 0.20
@rtyler what are you worried about in the interaction between Spark and Rust here? |
@ion-elgreco we don't have good round-trip tests with Spark writers and Rust writers collaborating (or not) with our log store implementation. |
@rtyler I see, but in this case I am not touching the S3DynamoDBLogStore, only S3 flavours that use copyIfNotExists or PutIfAbsent |
Description
When it's a default log store, we pass bytes around, for other log stores we keep the default tmp_commit logic in place (for stores like
S3DynamoDBLogStore
or the newS3LogStore
)Related Issue(s)