[ https://issues.apache.org/jira/browse/LUCENE-6226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14314241#comment-14314241 ]
Robert Muir commented on LUCENE-6226: ------------------------------------- {quote} I did not suggest anything for offsets/payloads on purpose to reduce the scope for now, but I don't think anything I suggest would be in the way of adding them in the future? {quote} They do add more complexity and "rules". For example, payloads today can be used by Span* to both determine matches and influence scoring. But these are lenient, nothing fails if they arent there, and allowed to be sparse: e.g. you could add a boost to only certain terms and a small segment might just happen to not have any payloads. On the other hand if you are asking for offsets, thats different. So +1 to just nailing down semantics for the positions case by itself for now. I do also like Alan's idea of making some small prototype, simplest possible thing (could be a test, doesnt matter) to try to actually test this stuff out too. > Allow TermScorer to expose positions, offsets and payloads > ---------------------------------------------------------- > > Key: LUCENE-6226 > URL: https://issues.apache.org/jira/browse/LUCENE-6226 > Project: Lucene - Core > Issue Type: Improvement > Reporter: Alan Woodward > Assignee: Alan Woodward > Fix For: Trunk, 5.1 > > Attachments: LUCENE-6226.patch, LUCENE-6226.patch, LUCENE-6226.patch, > LUCENE-6226.patch, LUCENE-6226.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org