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

Rename status stores to trackers #3895

Open
patchwork01 opened this issue Dec 10, 2024 · 0 comments
Open

Rename status stores to trackers #3895

patchwork01 opened this issue Dec 10, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request parent-issue An issue that is or should be split into multiple sub-issues
Milestone

Comments

@patchwork01
Copy link
Collaborator

patchwork01 commented Dec 10, 2024

Background

For checking the status of queries we use a store called the query tracker.

For checking the status of compaction and ingest jobs and tasks we use stores called the status stores.

We also have the state store, which sounds a lot like status store.

Description

We'd like to rename the compaction and ingest status stores to call them job trackers and task trackers instead, to distinguish them from the state store.

Analysis

We probably want to split this up to handle each status store separately. We'll need to make this change in the deployment of the underlying DynamoDB tables, in the actual implementation code, and in the reporting.

We'll also need to update the documentation everywhere the status stores are mentioned to call them job and task trackers instead.

We also need a bit more of the model of the trackers in the core module to include some of the data for a status update in a transaction. We could take this opportunity to rearrange the packages to put most of the status store core code into the core module in one place.

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

No branches or pull requests

2 participants