Stakeholders: Discovery Data Team and by extension Cirrus Engineers
Benefits: We can graph which requests got a suggestion
Estimate: An hour
Description
Description
Details
Details
Related Changes in Gerrit:
| Subject | Author | Repo | Branch | Lines +/- | |
|---|---|---|---|---|---|
| Log suggestion to requests log if there is one | Manybubbles | mediawiki/extensions/CirrusSearch | master | +4 -0 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Ironholds | T105910 EPIC: expansion of data retrieved from the Cirrus search logs | |||
| Resolved | None | T102040 In the zero results stream it'd be nice to know if the user was given a search suggestion | |||
| Resolved | None | T102042 Log whether or not the request returned a suggestion in the CirrusSearchRequests.log |
Event Timeline
Comment Actions
Change 217510 had a related patch set uploaded (by Manybubbles):
Log suggestion to requests log if there is one
Comment Actions
We might need a blocked, or canceled? iiuc the comments from @Ironholds on the patch indicate we shouldn't merge this. Each day i look over this patch to review column and this is still here, so feel like something needs to be done with it.
Comment Actions
My comments were "this won't break things so go nuts but we won't be consuming the data immediately because there's no task to track doing that, and if the goal is to have it analysed that needs to be a Dan-instituted task"