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

minor - gcs_prefix inconsistent with readme.md #15

Open
DevanM opened this issue Sep 14, 2020 · 1 comment
Open

minor - gcs_prefix inconsistent with readme.md #15

DevanM opened this issue Sep 14, 2020 · 1 comment

Comments

@DevanM
Copy link
Member

DevanM commented Sep 14, 2020

GCS_PREFIX in example_values/ethereum/trace_data/values.yaml inconsistent w/ readme step 4 (ethereum-etl/streaming/last_synced_block.txt)

GCS_PREFIX should read ethereum-etl/streaming
DevanM added a commit to DevanM/blockchain-etl-streaming that referenced this issue Sep 14, 2020
@DevanM
updating gcs prefix, issue blockchain-etl#15
6588dfb
@DevanM DevanM mentioned this issue Sep 14, 2020
Open
@voron
Copy link
Collaborator

voron commented Sep 14, 2020

Yes, readme doesn't cover how to proceed with [separate] traces streaming. We need to run one more etl-streaming instance to parse traces, and it stores it's state into separate last_synced_block.txt under gs://<YOUR_BUCKET_HERE>/ethereum-etl/streaming-trace. Thus, trace_data/values.yaml is correct, as GCS_PREFIX has to be different with block_data/values.yaml.

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
2 participants
@voron @DevanM