lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-3028) Support for additional query operators (feature parity request)
Date Fri, 03 Feb 2012 22:49:53 GMT

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

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

#1) maybe i'm missundertanding SOLR-2866 ... it talks about synonyms, but the crux of it is
really indexing multiple variants of a stemmed word with informatino about wether it is a
stem or not, and then being able to query on both -- your requrest seems to heavily overlap
with that -- in Victor's case he may be using a dictionary based stemmer, and in your case
you may want a hueristic stemmer, but the underlying plumbing should probably all be the same.

#2) sorry, yeah i missed your label and only looked at the example.  quorom search is definitely
possible using the dismax parse with the mm param, but there is no explicit syntax for it
in any parser i know of at the moment.

#3) the curly braces in that example were just me being explicit about which parser was in
use via local params -- that's not the query syntax.  you could just as easily do...

{code}
defType=surround&q=(this W that) AND (other W next)
{code}

In generallymy suggestion for moving forward would be to break these individual requests out
into 3 distinct issues since they are largely unrelated (or only open two issues and ask about
#1 in SOLR-2866 .. make an offshoot issue as needed)

individual issues with more direct issue summaries are easier to track and more likely to
encourage patches from people who see the summaries and realize it's something they are interested
in.
                
> 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


Mime
View raw message