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

Wire index/add handler to write derived hoverboard block level index #1405

Closed
Gozala opened this issue Apr 24, 2024 · 2 comments
Closed

Wire index/add handler to write derived hoverboard block level index #1405

Gozala opened this issue Apr 24, 2024 · 2 comments
Assignees

Comments

@Gozala
Copy link
Contributor

Gozala commented Apr 24, 2024

Context

Hoverboard facilitates reads over bitswap. It receives request for the block and looks up index in the dynamo prod-ep-v1-blocks-cars-position table which maps block multihash to CAR (bucket) paths. From the car path it derives CAR multihash and attempts to reads from preconfigured R2 and S3 buckets.

What

  • Derive block level index records from dag index, passed into implement index/add handler #1401, and write them into dynamo table.
  • ❗️Note that we should also create a record that spans the whole blob range even if it is not manually described in shards

Why

Otherwise content uploaded through blob/add will not be readable via bitswap

Deliverable

Reading blocks uploaded through blob/add and published via index/add should be readable via bitswap from web3.storage peer.

@Gozala
Copy link
Contributor Author

Gozala commented Apr 24, 2024

❗️Note that we should also create a record that spans the whole blob range even if it is not manually described in shards

I am just realizing that this may not be possible per current spec because size of the blob itself is not captured, we probably should amend spec to fix that

@alanshaw alanshaw self-assigned this Apr 29, 2024
@alanshaw
Copy link
Member

alanshaw commented May 8, 2024

resolved in storacha/w3infra#363

@alanshaw alanshaw closed this as completed May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants