-
Notifications
You must be signed in to change notification settings - Fork 32
fix: index migration and IPNI canAccept #684
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
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this 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)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Few comments
4b92f1e
to
338060b
Compare
338060b
to
d762bc7
Compare
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.