Tracking bug for simple queries. The queries are not stored yet in query entities, but directly executed. They allow to get all item ids who have a main snak with the given property and the value with the given property. Qualifiers and references are ignored.
This required the back end work, storing and updating the data in the respective secondary storage, querying that storage, an API module to give access to this, a special page for querying it.
Version: unspecified
Severity: major
Note: This has been highest priority (set by Lydia) for four months now.
Maybe the ticket's dependencies should be highest priority instead?
There are remaining bugs that need to be worked on. See the blockers. Then it needs to go through review at the Wikimedia Foundation again. I hope we have the main remaining blockers done in this and the next sprint.
Thanks for the update Lydia. Can you specify which of the "depends on" bugs are actual blockers? That will make it easier for external folks to get an idea of the actual status of things.
bug 67533, bug 67534, bug 67535, bug 67536, bug 71499, bug 71500, bug 71501, bug 71505 are the remaining blockers I know but more might pop up.
Meta comment: This has been "Highest" priority since 2013 (and hence has become "Unbreak now" priority in Phabricator). That sounds pretty unrealistic and I might remove that priority to have less clutter in the global "Unbreak now" search results.
It doesn't look like there has been any activity on any of the blockers for this bug in the past few months. Has this feature been deprioritized or abandoned in favor of Wikidata query service? We (WMF Mobile Web) would still really love to be able to use this feature in the short term if at all possible. If there's anything we can do to help, please let us know.
Yes this is on hold until further notice. We've put a ton of work into this feature that was dismissed in review before deployment. I can't put any more resources into moving this forward at this point if it is not even clear we will need it once the query service is working. Data quality tasks (ticket 76230) are highest priority for us at this point.
We decided that at this point the SPARQL endpoint is covering most usecases and is working well. The remaining usecase should be handled via T99899. I am therefore closing this.