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.

Sign up for GitHub

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

Jump to bottom

The latest sunk file is overwritten locally when resuming a stream. #3

Open
AngeloCa opened this issue Apr 21, 2023 · 2 comments
Open

The latest sunk file is overwritten locally when resuming a stream. #3

AngeloCa opened this issue Apr 21, 2023 · 2 comments

Comments

@AngeloCa
Copy link

Let's assume a stream is sunk until block 100000, as stated in issue #2, the latest file is 80000-90000.jsonl.

When resuming the sinking process to get the newest data (giving a new stop range e.g 120000), the latest file from the previous extraction (80000-90000.jsonl) is overwritten by an empty file.

Note: this behavior only appears when the output file path is a local path. (Sinking data to S3 doesn't overwrite the latest file)
@dkdocs
Copy link

dkdocs commented May 1, 2024

Any resolution on this issue?

@ArnaudBger
Copy link
Contributor

Hey @dkdocs it should be fixed, on the develop branch !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dkdocs @AngeloCa @ArnaudBger