Scholia (the main use case for the scholarly sub-graph) has requested an extension to ease the transition. While we don't have the resources to run a fully fledged full graph endpoint in parallel to the split endpoints, we should be able to provide a single server (lower availability and lower scalability), on a new dedicated endpoint, which would still expose the full graph for a transitional period. We expect that new endpoint to be available for a limited amount of time, probably until the end of December 2025.
Given the rate of queries requiring scholarly articles that we see in our logs, a single server should have enough capacity to handle the load.
We won't have any SLO on this new endpoint. With a single failure, any issue, or any maintenance operation will generate downtime. In particular, we will not be able to react to issues outside of working hours, so failures on a Friday are unlikely to be addressed until the following Monday.
AC
- DNS record create for query-legacy-full.wikidata.org
- Corresponding backend.yaml trafficserver routing config for query-legacy-full.wikidata.org/ (UI) and query-legacy-full.wikidata.org/sparql (sparql endpoint)
- Separate UI created for this purpose (include a header at the top of the page that explains that the service is temporary)