Closed
Bug 949050
Opened 12 years ago
Closed 9 years ago
Supersearch: allow faceting on multiple fields simultaneously
Categories
(Socorro :: Webapp, task, P3)
Socorro
Webapp
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: benjamin, Assigned: adrian)
References
Details
Right now in supersearch you can choose to facet on individual fields (even more than one individual field), but you cannot facet on multiple fields at the same time. I'd like to be able to do things like facet on buildid+signature or other combinations like that.
Really, being able to put multiple separate fields in the facet list is not as interesting to me, so I'd be fine with removing that from the UI if that makes it easier to do this version of multi-faceting.
| Assignee | ||
Updated•12 years ago
|
Assignee: nobody → adrian
OS: Linux → All
Hardware: x86_64 → All
| Reporter | ||
Comment 1•11 years ago
|
||
This is not possible with elasticsearch "facet" but it is possible with ES "aggregations".
See http://stackoverflow.com/questions/14181674/multiple-group-by-in-elasticsearch and http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-aggregations.html and http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-aggregations-bucket-terms-aggregation.html
I tried to run the following query as a prototype, but I'm hitting "oops, an error occurred". Adrian can you check the logs for me, or pass through more detailed errors messages on search/custom?
{
"filter": {
"and": [
{
"range": {
"processed_crash.date_processed": {
"gte": "2014-05-07T12:51:04+00:00"
}
}
},
{
"range": {
"processed_crash.date_processed": {
"lte": "2014-05-14T12:51:04+00:00"
}
}
},
{
"term": {
"processed_crash.signature.full": "js::jit::BaselineScript::nativeCodeForPC(JSScript*, unsigned char*, js::jit::PCMappingSlotInfo*)"
}
}
]
},
"aggregations": {
"channel": {
"terms": {
"field": "processed_crash.release_channel"
},
"aggregations": {
"build": {
"terms": {
"field": "processed_crash.build"
}
}
}
}
},
"size": 0
}
Flags: needinfo?(adrian)
| Assignee | ||
Comment 2•11 years ago
|
||
We are currently running elasticsearch 0.90, and aggregations are a new feature of ES 1.x. We will need to upgrade before you can use that feature. See bug 1010239.
Flags: needinfo?(adrian)
| Assignee | ||
Updated•11 years ago
|
Priority: -- → P3
| Assignee | ||
Comment 3•9 years ago
|
||
This works with the API, but won't be available in the UI unless really really needed. Hopefully that's enough.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 4•9 years ago
|
||
That's not great. The set of people who can hand-construct API queries is almost nil, and this isn't discoverable. What would it take to build the API for this?
| Reporter | ||
Updated•9 years ago
|
Flags: needinfo?(adrian)
| Assignee | ||
Comment 5•9 years ago
|
||
Considering that we are moving the data to Telemetry (tracker: bug 1273657), would it be doable with tools like spark and redash? I think it will be a waste of effort to add that feature to Super Search if we can do it in a few month in Telemetry.
Flags: needinfo?(adrian) → needinfo?(benjamin)
| Reporter | ||
Comment 6•9 years ago
|
||
Is the supersearch webpage going to continue to exist after the spark/redash transition? I don't really understand your project plan, but since ES already supports multi-faceting and it's very valuable for crash analysis, I feel like if we're going to keep supersearch at all, it should support this. We really don't need new UI: we just need to change the behavior of the existing UI to multi-facet instead of facet independently.
Flags: needinfo?(benjamin)
You need to log in
before you can comment on or make changes to this bug.
Description
•