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

Unify method signatures for synchronous and asynchronous commit #4262

Open
patchwork01 opened this issue Feb 14, 2025 · 0 comments
Open

Unify method signatures for synchronous and asynchronous commit #4262

patchwork01 opened this issue Feb 14, 2025 · 0 comments
Labels
parent-issue An issue that is or should be split into multiple sub-issues
Milestone

Comments

@patchwork01
Copy link
Collaborator

patchwork01 commented Feb 14, 2025

Background

For asynchronous commits to the state store, updates are submitted to TransactionLogStateStore.addTransaction. For synchronous commits, updates are done against a number of methods on the interfaces FileReferenceStoreUpdates and PartitionStore.

Description

We'd like to simplify how we make updates to the state store, whether they're done synchronously or asynchronously.

We'd like this to make it easier to move the job tracker updates from where they are now during synchronous updates, to being derived from the transaction log.

We'd like to remove the old methods for performing state store updates, and just keep addTransaction.

Analysis

This will be easier after the S3 state store implementation is removed:

We can split out separate issues for each method signature if necessary. Here are some possible changes:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
parent-issue An issue that is or should be split into multiple sub-issues
Projects
None yet
Development

No branches or pull requests

1 participant