Do you need it? Our workaround was to pass null, from what we could tell
the (lucene) QueryParser which is needs is only used for parsing UserQuery
constructs, and we never used that construct. The problem is that
SolrQueryParser is derived from Solr's QueryParser class which has now
diverged from the Lucene one.
Will try to get our patches updated and issued over Xmas.
On 17 December 2013 14:53, Puneet Pawaia <puneet.paw...@gmail.com> wrote:
> Hi All,
>
> Not being a Java expert, I used Daniel Collins' modification to patch with
> version 4.0 source. It works for a start. Have not been able to test much.
>
> Next, I tried the same modifications with Solr 4.6.0. This throws up 2
> errors.
>
> I resolved
> public Query parse() throws ParseException {
> by changing to
> public Query parse() throws SyntaxError {
>
> However, I am not able to get the second error resolved.
> SolrQueryParser lparser;
> CoreParser parser = new CoreParser(getReq().getSchema().getQueryAnalyzer(),
> lparser);
>
> CoreParser does not take SolrQueryParser as its parameter. It asks for
> QueryParser.
>
> Is there something I am missing or should be doing that I am not doing?
>
> TIA
>
> Regards
> Puneet
>
