We want to deploy simple query functionality for Wikidata. For this a performance review of WikibaseQueryEngine is needed. The code is at https://github.com/wmde/WikibaseQueryEngine.
Version: master
Severity: normal
Whiteboard: u=dev c=backend p=0
We want to deploy simple query functionality for Wikidata. For this a performance review of WikibaseQueryEngine is needed. The code is at https://github.com/wmde/WikibaseQueryEngine.
Version: master
Severity: normal
Whiteboard: u=dev c=backend p=0
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T52911 Support transitive queries | |||
| Resolved | None | T54387 Special page for querying by one property and value | |||
| Declined | Lydia_Pintscher | T54385 Query by one property and one value ("simple queries") (tracking) | |||
| Invalid | Lydia_Pintscher | T69535 performance review of WikibaseQueryEngine |
I'm a bit worried about the update script - it looks like it wants to directly modify the schema. It'd make more sense in our environment to spit out the SQL that would modify it.
Also, not to be a tool bigot - but it'd be neat to implement an Elasticsearch backed version of this - it'd be simpler in many ways. Probably more complex in others.
Re update script: we are aware of this. The CLI can already dump the schema creation code for exactly that purpouse
Note there is a test in the performance group that is excluded by default. I used this to get a quick idea of how quick inserts are, at least when there is little data in the store. https://github.com/wmde/WikibaseQueryEngine/blob/master/tests/Integration/PerformanceTest.php
Poke for status - I'm really just looking for some general hint on Ori would be able to start the review. Or if I should bounce to Aaron?
Some status on this - the tool is being rewritten to remove its dependency on external libraries. If possible it'd be cool to get started on the review before the rewrite. It _shouldn't_ be a huge rewrite - just replacing some of it.
the tool is being rewritten
It is not being "rewritten" - most of it will remain the same.
to remove its dependency on external libraries
That is being done, though does not involve rewriting the component.
I'm closing this for now as it is unclear if we're going to deploy it ever on the WMF cluster.