lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Philip <davidphilipshe...@gmail.com>
Subject Re: Queries not supported by Lucene Query Parser syntax
Date Thu, 01 Jan 2015 09:46:05 GMT
Hi Leonid,

   Have you had a look at edismax query parser[1]? Isn't that any use to
your requirement? I am not sure whether it is something that you are
looking for. But the question seemed to be having a query related to that.


[1] http://wiki.apache.org/solr/ExtendedDisMax#Query_Syntax



On Thu, Jan 1, 2015 at 2:38 PM, Leonid Bolshinsky <leonidbol@gmail.com>
wrote:

> Hello,
>
> Are we always limited by the query parser syntax when passing a query
> string to Solr?
> What about the query elements which are not supported by the syntax?
> For example, BooleanQuery.setMinimumNumberShouldMatch(n) is translated by
> BooleanQuery.toString() into ~n. But this is not a valid query syntax. So
> how can we express this via query syntax in Solr?
>
> And more general question:
> Given a Lucene Query object which was built programatically by a legacy
> code (which is using Lucene and not Solr), is there any way to translate it
> into Solr query (which must be a string). As Query.toString() doesn't have
> to be a valid Lucene query syntax, does it mean that the Solr query string
> must to be manually translated from the Lucene query object? Is there any
> utility that performs this job? And, again, what about queries not
> supported by the query syntax, like CustomScoreQuery, PayloadTermQuery
> etc.? Are we always limited in Solr by the query parser syntax?
>
> Thanks,
> Leonid
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message