[
https://issues.apache.org/jira/browse/LUCENE-5011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662946#comment-13662946
]
Simon Willnauer commented on LUCENE-5011:
-----------------------------------------
hey Itamar, can you provide a testcase that shows the issue? Providing your
analysis chain can be important here as well.
> MemoryIndex and FVH don't play along with multi-value fields
> ------------------------------------------------------------
>
> Key: LUCENE-5011
> URL: https://issues.apache.org/jira/browse/LUCENE-5011
> Project: Lucene - Core
> Issue Type: Bug
> Affects Versions: 4.3
> Reporter: Itamar Syn-Hershko
>
> When multi-value fields are indexed to a MemoryIndex, positions are computed
> correctly on search but the start and end offsets and the values array index
> aren't correct.
> Comparing the same execution path for IndexReader on a Directory impl and
> MemoryIndex (same document, same query, same analyzer, different Index impl),
> the difference first shows in FieldTermStack.java line 125:
> termList.add( new TermInfo( term, dpEnum.startOffset(), dpEnum.endOffset(),
> pos, weight ) );
> dpEnum.startOffset() and dpEnum.endOffset don't match between implementations.
> This looks like a bug in MemoryIndex, which doesn't seem to handle tokenized
> multi-value fields all too well when positions and offsets are required.
> I should also mention we are using an Analyzer which outputs several tokens
> at a position (a la SynonymFilter), but I don't believe this is related.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
