-
Notifications
You must be signed in to change notification settings - Fork 133
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
Add backfilling to search backed by GORM #294
Conversation
I haven't reviewed in depth, but i'm pretty darn excited about having a generic backfill mechanism like this! Great work. |
return | ||
} | ||
|
||
req.Header.Set("Accept", "application/vnd.ipld.car") |
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.
all this feels like it wants to be abstracted out a little. i assume you have a non-lexicon 'fetch repo' endpoint youre hitting?
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.
This is the lexicon GetCheckout endpoint, which we could do with an XRPC client and such but the body is just a raw CAR payload and we don't gain anything by using the lexicon and XRPC boilerplate here really... I don't even need this header to be honest.
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.
a few comments, the code could be cleaned up a bit, but i wont let that block anything
Search will need to backfill regularly when rebuilding indexes.
I've adopted a backfill pattern I created a few weeks ago into
indigo
and updated Search's firehose consuming to adopt the backfilling pattern.