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

Sunk data not corresponding to the requested range when using a stop block. #2

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

Sunk data not corresponding to the requested range when using a stop block. #2

AngeloCa opened this issue Apr 21, 2023 · 0 comments

Comments

@AngeloCa
Copy link

When using substreams-sink-file by specifying a stop block, sunk data has an extra block batch of delay ( a batch is equal to the number of blocks specified in --file-block-count).

Example: Let's assume a stream is sunk until block 105000 with --file-block-count 10000. We expect the latest sunk block to be 99999. However, when looking at the output, the latest file is range 80000-90000, and the latest block number in the state file is 89999.

To extract data until block 100000, we need to specify a stop block of 110000.
@AngeloCa AngeloCa changed the title Sinked data not corresponding to requested range when using stop block. Sunk data not corresponding to the requested range when using a stop block. Apr 21, 2023
@AngeloCa AngeloCa mentioned this issue Apr 21, 2023
Open
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
1 participant
@AngeloCa