Brief update:

We're still putting the final pieces in place for the cutover to the main
graph, so we're pushing to *Tuesday May 6 (2025-05-06)*.

Ryan

On Thu, May 1, 2025 at 9:44 PM Ryan Kemper <[email protected]> wrote:

> Hello Wikidata community,
>
> As mentioned in previous communications [1], we are continuing forward on
> the WDQS public graph split.
>
> The next stage of our rollout is to change query.wikidata.org to point to
> the main graph (which can also be reached directly on
> query-main.wikidata.org), whereas the scholarly graph will be available
> on query-scholarly.wikidata.org.
>
> Most queries should run fine on the appropriate graph (main vs scholarly),
> but for queries that must run across the full dataset, the queries must be
> (re)written to use SPARQL federation [2]. You can ask for help to rewrite
> your queries [3]. If you encounter issues please feel free to report a
> problem [4].
>
> If you need more time to do the transition you can use the new legacy
> endpoint [5] (query-legacy-full.wikidata.org) which contains the full
> Wikidata graph, but is limited in terms of performance and availability.
> Please be mindful when using this legacy endpoint and use it only if really
> needed. This endpoint will be available until December 2025.
>
> We are moving to this next stage on *Monday May 5* (*2025-05-05*).
>
> [1]
> https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/WDQS_backend_update/March_2025_scaling_update
> [2]
> https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/WDQS_graph_split/Internal_Federation_Guide
> [3] https://www.wikidata.org/wiki/Wikidata:Request_a_query
> [4] 
> https://www.wikidata.org/wiki/Wikidata:Report_a_technical_problem/WDQS_and_Search
>
> [5] https://phabricator.wikimedia.org/T384422
>
> Ryan
>
_______________________________________________
Wikidata mailing list -- [email protected]
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/[email protected]/message/CP3W6MSZQDPO6GXN475JODMRJ6G7RIUI/
To unsubscribe send an email to [email protected]

Reply via email to