-
Suggestion
-
Resolution: Won't Do
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Currently the default using of "Porter" stemming means that certain search phrases do not return results that the user might expect.
For example if the issue summary is "Moose problems" then the default stemming will cause "moos" to be stored in the index.
If the user then enters a search request for "Moose" then no match will be made. The reason is that the Lucene QueryParser code does NOT perform analysis on "Prefix" queries by default.
Hence a PrefixQuery for the term "moose" is submitted and the index doent contain this terms and hence no issue is returned.
The improvement would be to tweak QueryParser so that it does perform "analysis" on prefix queries. So the term "moose" would be stemmed to "moos" and then the Prefix Query would return the expected results.
- is related to
-
JRASERVER-13672 Better searching when stemming is in place. Improve Lucene QueryParser to perform analysis on prefixed queries.
- Closed
- relates to
-
JRACLOUD-17463 Better exact-text searching
- Gathering Interest
[JRACLOUD-13672] Better searching when stemming is in place. Improve Lucene QueryParser to perform analysis on prefixed queries.
Workflow | Original: JAC Suggestion Workflow [ 3154598 ] | New: JAC Suggestion Workflow 3 [ 3636422 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2340988 ] | New: JAC Suggestion Workflow [ 3154598 ] |
Component/s | New: Infrastructure & Services [ 46534 ] | |
Component/s | Original: Infrastructure & Services - Indexing [ 46521 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 2103987 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2340988 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2066700 ] | New: JIRA Bug Workflow w Kanban v6 [ 2103987 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 1848928 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2066700 ] |
Description |
Original:
Currently the default using of "Porter" stemming means that certain search phrases do not return results that the user might expect. For example if the issue summary is "Moose problems" then the default stemming will cause "moos" to be stored in the index. If the user then enters a search request for "Moose" then no match will be made. The reason is that the Lucene QueryParser code does NOT perform analysis on "Prefix" queries by default. Hence a PrefixQuery for the term "moose" is submitted and the index doent contain this terms and hence no issue is returned. The improvement would be to tweak QueryParser so that it does perform "analysis" on prefix queries. So the term "moose" would be stemmed to "moos" and then the Prefix Query would return the expected results. |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Cloud*. Using *JIRA Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRASERVER-13672]. {panel} Currently the default using of "Porter" stemming means that certain search phrases do not return results that the user might expect. For example if the issue summary is "Moose problems" then the default stemming will cause "moos" to be stored in the index. If the user then enters a search request for "Moose" then no match will be made. The reason is that the Lucene QueryParser code does NOT perform analysis on "Prefix" queries by default. Hence a PrefixQuery for the term "moose" is submitted and the index doent contain this terms and hence no issue is returned. The improvement would be to tweak QueryParser so that it does perform "analysis" on prefix queries. So the term "moose" would be stemmed to "moos" and then the Prefix Query would return the expected results. |
Link |
New:
This issue is related to |
Project Import | New: Sat Apr 01 19:36:47 UTC 2017 [ 1491075407146 ] |