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

[FEATURE]: Allow holding back specific timestamps #2055

Open
Adphi opened this issue Apr 5, 2024 · 1 comment
Open

[FEATURE]: Allow holding back specific timestamps #2055

Adphi opened this issue Apr 5, 2024 · 1 comment
Labels
kind/feature Something completely new we should consider. Stale

Comments

@Adphi
Copy link

Adphi commented Apr 5, 2024

Have you tried Badger before this proposal? and did not find anything similar?

Yes

What you wanted to do.

To overcome the transaction size limitation, we are forced to use batch writes. But there is no way to rollback the created transactions in case of error. In addition, the transactions created automatically will be readable before the entire batch is written, which is not necessarily desirable.

What you actually did.

No response

Why wasn't it great, with examples.

No response

Additional information.

Badger could use a list of timestamps that will not be readable, in the same way that there are banned namespaces. These ignored (or pending) timestamps would not be readable until they were marked as ready.

@Adphi Adphi added the kind/feature Something completely new we should consider. label Apr 5, 2024
@Adphi Adphi changed the title [FEATURE]: Allow holding back a specific timestamp [FEATURE]: Allow holding back specific timestamps Apr 5, 2024
Copy link

This issue has been stale for 60 days and will be closed automatically in 7 days. Comment to keep it open.

@github-actions github-actions bot added the Stale label Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Something completely new we should consider. Stale
Development

No branches or pull requests

1 participant