Page MenuHomePhabricator

Support qlever endpoint for integraality
Closed, ResolvedPublic

Description

Qlever is an alternative SPARQL endpoint for Wikidata data. The updates are not real time ; but it is considerably faster than WDQS. It would unlock using integraality for datasets that are too big/complex for WDQS.

Open questions: would this be only for the dashboard-building, or also for the looking-glass (aka queries endpoint).

Related Objects

Event Timeline

Qlever is approaching being able to support real-time updates, and is being more widely used by various wikidata-related initiatives as well as those involving larger datasets. This would be excellent.

Mentioned in SAL (#wikimedia-cloud) [2025-10-29T12:32:05Z] <wmbot~jeanfred@tools-bastion-15> Deploy 4da9f33 (Implement SPARQL query engine dependency injection) for T385749

Mentioned in SAL (#wikimedia-cloud) [2025-10-29T12:32:24Z] <wmbot~jeanfred@tools-bastion-15> Deploy f34624d (Move pywikibot exception handling to SPARQL engine class) for T385749

Mentioned in SAL (#wikimedia-cloud) [2025-10-29T16:48:58Z] <wmbot~jeanfred@tools-bastion-15> Deploy be5c234 (Add support for QLever as alternative SPARQL query engine) for T385749

Mentioned in SAL (#wikimedia-cloud) [2025-10-29T16:49:05Z] <wmbot~jeanfred@tools-bastion-15> Deploy 4cc2bcc (Add configurable SPARQL endpoint support for QLever in PagesProcessor) for T385749

Mentioned in SAL (#wikimedia-cloud) [2025-10-29T16:49:13Z] <wmbot~jeanfred@tools-bastion-15> Deploy 28c2e1b (Add link to QLever on queries error page) for T385749

JeanFred claimed this task.

This is now done, as present for Wikidata’s 13th birthday :)

  • Using sparql_endpoint=qlever will make integraality use QLever instead of Wikidata Query Service
  • On the error page for when a SPARQL query fails, a link to QLever will be provided alongside WDQS
  • the queries endpoint will provide links to both WDQS and QLever

See example at https://www.wikidata.org/wiki/Wikidata:WikiProject_sum_of_all_paintings/Property_statistics/Sandbox

I have a couple of fixes to do, but this is good as done :)

Mentioned in SAL (#wikimedia-cloud) [2025-11-03T17:19:31Z] <wmbot~jeanfred@tools-bastion-15> Deploy 2d3e128 (Display the name of the SPARQL endpoint used in the edit summary) for T385749

Mentioned in SAL (#wikimedia-cloud) [2025-11-03T17:19:47Z] <wmbot~jeanfred@tools-bastion-15> Deploy 2d3e128 (Display the name of the SPARQL endpoint used in the edit summary) for T385749

Just noticing this, hurrah :) Love to see it.

Mentioned in SAL (#wikimedia-cloud) [2026-03-05T18:44:09Z] <wmbot~jeanfred@tools-bastion-15> Deploy 28d800e (Extract rdfs:label SPARQL fragment from grouping.py to get_label_for_variable utility), 40c39de (Make intermediate label variables unique to avoid clashes in get_label_for_variable) and 64e8f94 (Replace SERVICE wikibase:label with native SPARQL for QLever compatibility) for T385749