This is a tracking task for changes that will require Blazegraph data store reload. Since it makes sense to group their fixing into as little batches as possible, they are listed here:
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Gehel | T222404 Tasks requiring Blazegraph reload | |||
| Resolved | Gehel | T228122 DB reload for WDQS |
Event Timeline
Comment Actions
@Smalyshev: This task really never ends and will remain open forever? Is there a reason there are no subtasks?
Comment Actions
@Aklapper the idea is to track all the tasks that need full DB reload in one place. Since conceivably these tasks will be also popping up in the future, it will not be closed. If that's a problem, we could have separate task for each reload cycle, but we've been doing it for search with T147505 and it seems to work well. Suggestions welcome of course.
Comment Actions
Thanks for the explanation. Interesting because T147505 does not have a Tracking-Neverending tag. (And I asked because it's deprecated.)