[jira] [Commented] (SOLR-3028) Support for additional query operators (feature parity request)

["Hoss Man (Commented) (JIRA)" <ji...@apache.org>]

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

Hoss Man commented on SOLR-3028:
--------------------------------


#1) you can either index both stemmed and non-stemed in diff fields, and then specify the appropriate field name at query time for each input word to control what gets queried, or something like SOLR-2866 would be needed along with additional filters to record in the terms whether it's stemmed/unstemmed (possible with the payload?) so it's available at query time

#2) already possible with the standard lucene syntax: "cat doc goat"~15

#3) is already possible on trunk with the surround parser (SOLR-2703) -- although there isn't a lot of documentation out there about the syntax...

{code}
  {!surround}(this W that) AND (other W next) 
{code}

...it seems like the only real missing piece is some query side support for SOLR-2866, and it seems like that would best be tracked in SOLR-2866 right? ... make sure everything works all the way through the system?
                
> Support for additional query operators (feature parity request)
> ---------------------------------------------------------------
>
>                 Key: SOLR-3028
>                 URL: https://issues.apache.org/jira/browse/SOLR-3028
>             Project: Solr
>          Issue Type: Improvement
>          Components: search
>    Affects Versions: 4.0
>            Reporter: Mike
>              Labels: operator, queryparser
>   Original Estimate: 6h
>  Remaining Estimate: 6h
>
> I'm migrating my system from Sphinx Search, and there are a couple of operators that are not available to Solr, which are available in Sphinx. 
> I would love to see the following added to the Dismax parser:
> 1. Exact match. This might be tricky to get right, since it requires work on the index side as well[1], but in Sphinx, you can do a query such as [ =running walking ], and running will have stemming off, while walking will have it on. 
> 2. Term quorum. In Sphinx and some commercial search engines (like Recommind, Westlaw and Lexis), you can do a search such as [ (cat dog goat)/15 ], and find the three words within 15 terms of each other. I think this is possible in the backend via the span query, but there's no front end option for it, so it's quite hard to reveal to users.
> 3. Word order. Being able to say, "this term before that one, and this other term before the next" is something else in Sphinx that span queries support, but is missing in the query parser. Would be great to get this in too.
> These seem like the three biggest missing operators in Solr to me. I would love to help move these forward if there is any way I can help.
> [1] At least, *I* think it does. There's some discussion of one way of doing exact match like support in SOLR-2866.

--
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org