Page MenuHomePhabricator

wdqs v2: Setup internal routing for query federation between main and scholarly
Open, MediumPublic3 Estimated Story Points

Description

We need to test and adjust routing for internal and external federation.

  • UA enforcement to be considered for external only, meaning requests from query-next and query-scholarly-next should not be UA-gated.
  • Verify the possibility to enforce/change the UA on Qlever federation requests.

Test query (TODO: better test query with less results which make it obvious that federation actually works):

SELECT ?item ?bhl_id WHERE {
  { 
    ?item wdt:P4327 ?bhl_id . 
  }
  UNION
  {
    SERVICE <http://query-scholarly-next.wikidata.org/sparql> {
      ?item wdt:P4327 ?bhl_id . 
    } 
  }
}

AC

  • query-external and query-scholarly-external public endpoints can federate with each other

Event Timeline

gmodena renamed this task from wdqs v2: test external and internal federation to [NEEDS GROOMING] wdqs v2: test external and internal federation.Jul 15 2026, 1:47 PM
trueg renamed this task from [NEEDS GROOMING] wdqs v2: test external and internal federation to wdqs v2: Setup internal routing for query federation between main and scholarly.Jul 15 2026, 2:18 PM
trueg triaged this task as High priority.
trueg lowered the priority of this task from High to Medium.
trueg updated the task description. (Show Details)
trueg set the point value for this task to 3.
lerickson subscribed.

Current status: federation allowlist updates from Sebastian's MR above have been deployed on staging for both main and scholarly. Still need to do it in prod.