Closed Bug 668621 Opened 14 years ago Closed 14 years ago

'has terms' in the stack signature field of the advanced query should be removed

Categories

(Socorro :: General, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: lonnen, Assigned: adrian)

Details

(Whiteboard: [stage])

Attachments

(1 file)

The 'has terms' option in the stack signature search field returns a result that is neither intuitive nor equivalent to other search queries with a postgres back end. It is functionally equivalent to "starts with" when we're using an elastic search back end. I would advocate removing it as an option.
I was wrong above. It is supposed to be equivalent to 'starts with' when we're using postgres, and behaves uniquely on an elastic search back end. It doesn't appear to actually be equivalent. It should be removed for this release.
Remove "has terms" search option for the UI when using Postgres on the back-end.
Assignee: nobody → adrian
Attachment #543239 - Flags: review?(rhelmer)
Attachment #543239 - Flags: review?(chris.lonnen)
Attachment #543239 - Flags: review?(chris.lonnen) → review+
Attachment #543239 - Flags: review?(rhelmer) → review+
Committed rev 3263/3264
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2.0
This looks good on stage, where Postgres is installed. Have we been able to verify that "has terms" is visible on a box running Elastic Search? Or am I understanding the patch incorrectly, attachment 54323 [details] [diff] [review]?
Verified that it appears on a server configured to use an Elastic Search back end.
Thanks lonnen. QA verified per comment 4 and comment 5.
Status: RESOLVED → VERIFIED
Component: Socorro → General
Product: Webtools → Socorro
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: