I have declared the rerank query parser and executed it.
Works under 7.1, but does not work under 7.2. The same copied config file.
Under 7.2 I receive the same exception "rq parameter must be a RankQuery"
as for ltr.

And I am sure I've declared it correctly, because in 7.1 it even complained
if I missed to pass it's rerank query. Worked if the query was passed.
With 7.2 it does not come to this point, it does not understand what rerank
is and throws the exception above.

Best regards,
Dariusz Wojtas


On Fri, Dec 29, 2017 at 10:57 AM, Diego Ceccarelli (BLOOMBERG/ LONDON) <
dceccarel...@bloomberg.net> wrote:

> Dariusz, does the rerank query work?
>
> From: solr-user@lucene.apache.org At: 12/28/17 22:25:28To:
> solr-user@lucene.apache.org
> Subject: Re: SOLR 7.2 and LTR
>
> Yes, this could be SOLR-11501.
> But from the description in the ticket I see no option to run LTR, unless I
> am missing something.
>
> I have the ltr queryParser registered. I believe it is declared correctly,
> works with 7.0.0.
> I have just double checked with different SOLR versions, copying exactly
> the same config directory to each 'server/solr' directory.
> * SOLR 7.0.0 - works
> * SOLR 7.1.0 - works
> * SOLR 7.2.0 - does not work, exception as previously described.
>
> I have tried to run it with
> *  'luceneMatchVersion' => 7.0.0, 7.1.0 and 7.2.0. It does not change
> anything.
> * <str name="uf">*,_query_</str> defined in initParams
> * defType=ltr, but then the main query, which is of type edismax, cannot be
> instantiated because of NPE
>
> Any Hint how to use LTR with 7.2?
>
>
> Best regards,
> Dariusz Wojtas
>
>
> On Thu, Dec 28, 2017 at 6:11 PM, Christine Poerschke (BLOOMBERG/ LONDON) <
> cpoersc...@bloomberg.net> wrote:
>
> > From a (very) quick look it seems like the https://issues.apache.org/
> > jira/browse/SOLR-11501 upgrade notes might be relevant, potentially.
> >
> > From: solr-user@lucene.apache.org At: 12/28/17 15:18:22To:
> > solr-user@lucene.apache.org
> > Subject: Re: SOLR 7.2 and LTR
> >
> > Do you have the ltr qparser plugin registered into the solrconfig?
> >
> > Can you check what happens if instead of ltr you use the rerank query
> > plugin? does it work or you get the same error?
> > https://lucene.apache.org/solr/guide/6_6/query-re-ranking.html
> >
> >
> > From: solr-user@lucene.apache.org At: 12/28/17 13:58:26To:
> > solr-user@lucene.apache.org
> > Subject: Re: SOLR 7.2 and LTR
> >
> > Hello Diego,
> >
> > solr.log contains always the same single stacktrace in SOLR 7.2.
> > I've been trying to pass rq via solrconfig.xml and via HTTP form.
> > The /searchIncidents handler contains edismax query.
> > Works if I completely disable rq. When I add the rq param, even something
> > like:
> >    {!ltr reRankDocs=25 model=incidentModel}
> > I get the exception.
> > The model is there, it's LinearModel model simplified to contain only
> > single feature 'originalScore', defined as in all available examples.
> > I just copy the same config directory under 'server\solr' to SOLR 7.0 and
> > it works.
> > I only skip the 'data' subfolder because of index differences, wen
> copying.
> >
> > 2017-12-28 13:51:08.141 DEBUG (qtp205125520-18) [   x:entityindex]
> > o.a.s.c.S.Request [entityindex]  webapp=/solr path=/searchIncidents
> > params={personalId=1234567890&searchedTerms=Test&rq={!ltr+
> > reRankDocs%3D25+model%3DincidentModel}}
> > 2017-12-28 13:51:08.145 ERROR (qtp205125520-18) [   x:entityindex]
> > o.a.s.h.RequestHandlerBase org.apache.solr.common.SolrException: rq
> > parameter must be a RankQuery
> > at
> > org.apache.solr.handler.component.QueryComponent.
> > prepare(QueryComponent.java:183)
> > at
> > org.apache.solr.handler.component.SearchHandler.handleRequestBody(
> > SearchHandler.java:276)
> > at
> > org.apache.solr.handler.RequestHandlerBase.handleRequest(
> > RequestHandlerBase.java:177)
> > at org.apache.solr.core.SolrCore.execute(SolrCore.java:2503)
> > at org.apache.solr.servlet.HttpSolrCall.execute(HttpSolrCall.java:710)
> > at org.apache.solr.servlet.HttpSolrCall.call(HttpSolrCall.java:516)
> > at
> > org.apache.solr.servlet.SolrDispatchFilter.doFilter(
> > SolrDispatchFilter.java:382)
> > at
> > org.apache.solr.servlet.SolrDispatchFilter.doFilter(
> > SolrDispatchFilter.java:326)
> > at
> > org.eclipse.jetty.servlet.ServletHandler$CachedChain.
> > doFilter(ServletHandler.java:1751)
> > at
> > org.eclipse.jetty.servlet.ServletHandler.doHandle(
> ServletHandler.java:582)
> > at
> > org.eclipse.jetty.server.handler.ScopedHandler.handle(
> > ScopedHandler.java:143)
> > at
> > org.eclipse.jetty.security.SecurityHandler.handle(
> > SecurityHandler.java:548)
> > at
> > org.eclipse.jetty.server.session.SessionHandler.
> > doHandle(SessionHandler.java:226)
> > at
> > org.eclipse.jetty.server.handler.ContextHandler.
> > doHandle(ContextHandler.java:1180)
> > at org.eclipse.jetty.servlet.ServletHandler.doScope(
> > ServletHandler.java:512)
> > at
> > org.eclipse.jetty.server.session.SessionHandler.
> > doScope(SessionHandler.java:185)
> > at
> > org.eclipse.jetty.server.handler.ContextHandler.
> > doScope(ContextHandler.java:1112)
> > at
> > org.eclipse.jetty.server.handler.ScopedHandler.handle(
> > ScopedHandler.java:141)
> > at
> > org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(
> > ContextHandlerCollection.java:213)
> > at
> > org.eclipse.jetty.server.handler.HandlerCollection.
> > handle(HandlerCollection.java:119)
> > at
> > org.eclipse.jetty.server.handler.HandlerWrapper.handle(
> > HandlerWrapper.java:134)
> > at
> > org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(
> > RewriteHandler.java:335)
> > at
> > org.eclipse.jetty.server.handler.HandlerWrapper.handle(
> > HandlerWrapper.java:134)
> > at org.eclipse.jetty.server.Server.handle(Server.java:534)
> > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320)
> > at
> > org.eclipse.jetty.server.HttpConnection.onFillable(
> > HttpConnection.java:251)
> > at
> > org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(
> > AbstractConnection.java:283)
> > at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:108)
> > at
> > org.eclipse.jetty.io.SelectChannelEndPoint$2.run(
> > SelectChannelEndPoint.java:93)
> > at
> > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.
> > executeProduceConsume(ExecuteProduceConsume.java:303)
> > at
> > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.
> > produceConsume(ExecuteProduceConsume.java:148)
> > at
> > org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(
> > ExecuteProduceConsume.java:136)
> > at
> > org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(
> > QueuedThreadPool.java:671)
> > at
> > org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(
> > QueuedThreadPool.java:589)
> > at java.lang.Thread.run(Unknown Source)
> >
> > Best regards,
> > Dariusz Wojtas
> >
> >
> > On Thu, Dec 28, 2017 at 1:03 PM, Diego Ceccarelli (BLOOMBERG/ LONDON) <
> > dceccarel...@bloomberg.net> wrote:
> >
> > > Hello Dariusz,
> > >
> > > Can you look into the solr logs for a stack trace or ERROR logs?
> > >
> > >
> > >
> > > From: solr-user@lucene.apache.org At: 12/27/17 19:01:29To:
> > > solr-user@lucene.apache.org
> > > Subject: SOLR 7.2 and LTR
> > >
> > > Hi,
> > >
> > > I am using SOLR 7.0 and use the ltr parser.
> > > The configuration I use works nicely under SOLR 7.0.0.
> > > I am trying to upgrade to 7.2.0 but whenever I want to use my handler,
> I
> > > get an exception:
> > > "rq parameter must be a RankQuery"
> > >
> > > The exact response is:
> > > <lst name="error">
> > > <lst name="metadata">
> > > <str name="error-class">org.apache.solr.common.SolrException</str>
> > > <str name="root-error-class">org.apache.solr.common.
> SolrException</str>
> > > </lst>
> > > <str name="msg">rq parameter must be a RankQuery</str>
> > > <intname="code">400</int>
> > > </lst>
> > >
> > >
> > > My rq param is:
> > > <str name="rq">{!ltr reRankDocs=25 model=myModel}</str>
> > >
> > > I have simplified the model (Linear) to contain only single feature
> > > "originalScore".
> > > Works under 7.0, but when I run it with 7.2 - error.
> > >
> > > Any hints on this?
> > >
> > >
> > >
> >
> >
> >
>
>
>

Reply via email to