Skip to content

Conversation

LexLuthr
Copy link
Contributor

@LexLuthr LexLuthr commented Oct 7, 2025

I will be dropping index migration due to high op cost for now. This PR will add some conversion to allow v1 and v2 lookup both.

@LexLuthr LexLuthr requested a review from a team as a code owner October 7, 2025 15:48
Copy link
Collaborator

@magik6k magik6k left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CanAccept makes sense to me.

Little worried about performance in UpdatePieceCidV1ToV2, that reads like it can cause some serious problems for larger SPs with 100s of billions of index entries (i.e. pib-scale or with blockchain data)

@LexLuthr LexLuthr linked an issue Oct 8, 2025 that may be closed by this pull request
Copy link
Collaborator

@magik6k magik6k left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Few comments

@LexLuthr LexLuthr force-pushed the fix/mk20-indexing branch 2 times, most recently from 4b92f1e to 338060b Compare October 10, 2025 08:06
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

Successfully merging this pull request may close these issues.

Fix indexing piece cid v1 to v2 migration

2 participants