Skip to content
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

Merged
merged 7 commits into from
Aug 23, 2024

Conversation

ion-elgreco
Copy link
Collaborator

@ion-elgreco ion-elgreco commented Aug 22, 2024

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 new S3LogStore)

Related Issue(s)

@ion-elgreco ion-elgreco changed the title feat: condtional put feat: condtional put for default log store (azure, gcs) Aug 22, 2024
@github-actions github-actions bot added the binding/rust Issues for the Rust crate label Aug 22, 2024
@ion-elgreco ion-elgreco changed the title feat: condtional put for default log store (azure, gcs) feat: condtional put for default log store (e.g. azure, gcs) Aug 22, 2024
@ion-elgreco ion-elgreco changed the title feat: condtional put for default log store (e.g. azure, gcs) feat: conditional put for default log store (e.g. azure, gcs) Aug 22, 2024
@ion-elgreco ion-elgreco marked this pull request as draft August 22, 2024 11:04
@ion-elgreco ion-elgreco marked this pull request as ready for review August 22, 2024 12:38
@ion-elgreco ion-elgreco changed the title feat: conditional put for default log store (e.g. azure, gcs) perf: conditional put for default log store (e.g. azure, gcs) Aug 22, 2024
@ion-elgreco ion-elgreco changed the title perf: conditional put for default log store (e.g. azure, gcs) perf: conditional put for default log store (e.g. azure, gcs, minio, cloudflare) Aug 22, 2024
Copy link
Member

@rtyler rtyler left a 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

@ion-elgreco ion-elgreco added this pull request to the merge queue Aug 23, 2024
Merged via the queue into delta-io:main with commit 53749f0 Aug 23, 2024
21 checks passed
@ion-elgreco ion-elgreco deleted the feat/conditional_put branch August 23, 2024 14:41
@ion-elgreco
Copy link
Collaborator Author

ion-elgreco commented Aug 23, 2024

@rtyler what are you worried about in the interaction between Spark and Rust here?

@rtyler
Copy link
Member

rtyler commented Aug 23, 2024

@ion-elgreco we don't have good round-trip tests with Spark writers and Rust writers collaborating (or not) with our log store implementation.

@ion-elgreco
Copy link
Collaborator Author

ion-elgreco commented Aug 23, 2024

@rtyler I see, but in this case I am not touching the S3DynamoDBLogStore, only S3 flavours that use copyIfNotExists or PutIfAbsent

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
binding/rust Issues for the Rust crate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Option To Use ObjectStore Conditional Put
4 participants