Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-11180

OriginalScoreFeature always returns 0.0 with SolrCloud mode.

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 6.5
    • 7.1, 8.0
    • contrib - LTR
    • None
    • Repro on SolrCloud mode. Working ok with a standalone instance.

    Description

      This bug is related to SOLR-11164.

      org.apache.solr.ltr.feature.OriginalScoreFeature is always returning 0.0 when configured LTR features are evaluated within a SolrCloud cluster.

      {
      	"responseHeader": {
      		"zkConnected": true,
      		"status": 0,
      		"QTime": 10,
      		"params": {
      			"q": "test",
      			"fl": "id,score,[features]"
      		}
      	},
      	"response": {
      		"numFound": 2,
      		"start": 0,
      		"maxScore": 1.7527907,
      		"docs": [
      			{
      				"id": "GB18030TEST",
      				"[features]": "originalScore=0.0",
      				"score": 1.7527907
      			},
      			{
      				"id": "UTF8TEST",
      				"[features]": "originalScore=0.0",
      				"score": 1.5209608
      			}
      		]
      	}
      }
      

      Furthermore, is throwing an exception when the query parser is used.

      {
      	"responseHeader": {
      		"zkConnected": true,
      		"status": 500,
      		"QTime": 18,
      		"params": {
      			"q": "test",
      			"fl": "id,score,[features]",
      			"rq": "{!ltr model=model reRankDocs=100}"
      		}
      	},
      	"error": {
      		"metadata": [
      			"error-class",
      			"org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException",
      			"root-error-class",
      			"org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException"
      		],
      		"msg": "Error from server at http://someip:8983/solr/gettingstarted_shard2_replica1: Server Error\n\nrequest: http://someip:8983/solr/gettingstarted_shard2_replica1/query",
      		"trace": "org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error from server at http://someip:8983/solr/gettingstarted_shard2_replica1: Server Error\n\nrequest: http://someip:8983/solr/gettingstarted_shard2_replica1/query\r\n\tat org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:610)\r\n\tat org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:279)\r\n\tat org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:268)\r\n\tat org.apache.solr.client.solrj.SolrClient.request(SolrClient.java:1219)\r\n\tat org.apache.solr.handler.component.HttpShardHandler.lambda$submit$0(HttpShardHandler.java:163)\r\n\tat java.util.concurrent.FutureTask.run(FutureTask.java:266)\r\n\tat java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)\r\n\tat java.util.concurrent.FutureTask.run(FutureTask.java:266)\r\n\tat com.codahale.metrics.InstrumentedExecutorService$InstrumentedRunnable.run(InstrumentedExecutorService.java:176)\r\n\tat org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.lambda$execute$0(ExecutorUtil.java:229)\r\n\tat java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)\r\n\tat java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)\r\n\tat java.lang.Thread.run(Thread.java:745)\r\n",
      		"code": 500
      	}
      }
      

      Attached a file with a sample on how to repro:

      • Use bin\solr -e cloud -Dsolr.ltr.enabled=true to create a sample SolrCloud with techproducts.
      • Features file with only OriginalScoreFeature
      • Simple model using that feature.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            cpoerschke Christine Poerschke
            Jonathan GV Jonathan Gonzalez
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment