daniel added a comment.
I'm very sceptical about using SPARQL for this. It does not seem to be the right tool at all. We should use Elastic instead, with a fallback to the old SQL based system. From the task description, it's unclear to me which problem it aims to solve, and also what exactly the proposed solution is, except "use SPARQL somehow". If I understand correctly, the proposed use case is a //search//, not a //query//. Searches return an open-ended result, ordered by some heuristic score, potentially including inexact matches. SPARQL doesn't do that (at least not simply or efficiently). It's meant for queries that return a well defined set of results. TASK DETAIL https://phabricator.wikimedia.org/T132030 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: daniel Cc: aude, daniel, hoo, Lydia_Pintscher, Tpt, Smalyshev, Jonas, Aklapper, Avner, debt, Gehel, D3r1ck01, FloNight, Izno, jkroll, Wikidata-bugs, Jdouglas, Deskana, Manybubbles, Mbch331 _______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
