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

The new indexing service returns content claims for data added with blob protocol but published to legacy content claims DB #7

Open
hannahhoward opened this issue Sep 23, 2024 · 0 comments
Assignees

Comments

@hannahhoward
Copy link
Member

hannahhoward commented Sep 23, 2024

What

When I query for blobs added before the indexing service is released, the indexing service should be able to read legacy content claims for indexes from the database. It should also asynchronously added them to the IPNI advertisement chain.

@hannahhoward hannahhoward changed the title the new indexing service should publish on demand existing sharded dag indexes and location claims The new indexing service returns content claims for data added with blob protocol but published to content claims and converts on demand to IPNI publish Sep 23, 2024
@hannahhoward hannahhoward changed the title The new indexing service returns content claims for data added with blob protocol but published to content claims and converts on demand to IPNI publish The new indexing service returns content claims for data added with blob protocol but published to legacy content claims DB Sep 23, 2024
@hannahhoward hannahhoward self-assigned this Sep 25, 2024
@hannahhoward hannahhoward transferred this issue from storacha/project-tracking Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Sprint Backlog
Development

No branches or pull requests

1 participant