[ 
https://issues.apache.org/jira/browse/SOLR-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251844#comment-13251844
 ] 

Jan Høydahl commented on SOLR-3099:
-----------------------------------

The duplicate field trick is well known. This issue is specifically about 
*exploring* native support in the original field for this. A native solution 
*will* save space, be easier to understand/use, be more performant, support 
more query features (such as spans) etc. This is a community; please let's try 
to contribute towards a improving the design instead of dismissing it as "not 
the way to go".
                
> Add query operator, index structure, and analyzer for "exact match" searching
> -----------------------------------------------------------------------------
>
>                 Key: SOLR-3099
>                 URL: https://issues.apache.org/jira/browse/SOLR-3099
>             Project: Solr
>          Issue Type: Sub-task
>          Components: Schema and Analysis
>            Reporter: Mike
>             Fix For: 4.0
>
>
> A project I'm working on requires *exact match* searching with stemming 
> turned off. The users are accostomed to Sphinx search, and thus expect a 
> query like [ =runs ] to return only documents that contain the exact term, 
> "runs", and not the stemmed word "run".
> In SOLR-2866, there is similar work, but I believe it is different because it 
> uses a huge-synonym file rather than storing the original terms directly in 
> the index. 
> What I'd like instead is two things:
> 1. An analyzer that says, "store the original form of all words in the index 
> along with the stemmed variations." If necessary, it's fine if this is simply 
> an unstemmed field, but that seems cumbersome schema-wise and 
> performance-wise.
> 2. An operator in edismax that allows users to query the exact form of the 
> word. Sphinx uses the equals sign (=), and that makes sense logically to me.
> This issue is part of a meta issue, SOLR-3028, that is requesting two other 
> operators in edismax (quorum search and word order).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to