Hello Leonid,
Yep. This problem exists and makes hard the migration from Lucene to Solr.
You might be interested in Parboiled
http://www.youtube.com/watch?v=DXiRYfFGHJE
The simplest way to solve it is to serialize Lucene Query instance into
parameter or request body. Unfortunately, Query is not Se
Hi Lenoid,
Here is another un-committed parser :
https://issues.apache.org/jira/browse/LUCENE-5205
Ahmet
On Thursday, January 1, 2015 5:59 PM, Roman Chyla wrote:
Hi Leonid,
I didn't look into solr qparser for a long time, but I think you should be
able to combine different query parsers i
Hi Leonid,
I didn't look into solr qparser for a long time, but I think you should be
able to combine different query parsers in one query. Look at the
SolrQueryParser code, maybe now you can specify custom query parser for
every clause (?), st like:
foo AND {!lucene}bar
I dont know, but worth e
Yes, you are always limited by the query parser syntax, but of course you
can always write your own query parser as well.
There is an open issue for an XML-based query parser that would give you
greater control. but... it's not committed yet:
https://issues.apache.org/jira/browse/SOLR-839
-- Jack
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 Th
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
