[ https://issues.apache.org/jira/browse/SOLR-10874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049777#comment-16049777 ]
Michael Kosten commented on SOLR-10874: --------------------------------------- You're not seeing it in the wild because assertions aren't enabled. I tried running solr in the wild with assertions enabled (which I don't think anyone would do normally), but it failed due to another assertion, so I can't get it to the point of executing a query with the payload function. However, when you do run in in the wild, the explain output is wrong, it shows 0.0 for the results of the payload function. You can see it in your comment above for doc 1: "product of:\n 0.0 = payload(vals_dpf,one,const(0.0))=0.0". I traced what happens when debug is true. The floatVal is called 3 times sequentially for each doc in the explain output. > FloatPayloadValueSource throws assertion error if debug=true > ------------------------------------------------------------ > > Key: SOLR-10874 > URL: https://issues.apache.org/jira/browse/SOLR-10874 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Components: search > Affects Versions: 6.6 > Reporter: Michael Kosten > Assignee: Erik Hatcher > Priority: Minor > Fix For: master (7.0), 6.7, 6.6.1 > > Attachments: SOLR-10874.patch > > Original Estimate: 2h > Remaining Estimate: 2h > > Using the new payload function will fail with an assertion error if the debug > parameter is included in the query. This is caused by the floatValue method > in FloatPayloadValueSource being called for the same doc id twice in a row. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org