[
https://issues.apache.org/jira/browse/LUCENE-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13169289#comment-13169289
]
Simon Willnauer commented on LUCENE-3647:
-----------------------------------------
my first guess is that this comes due to the different IWCs if you don't
specify a value for a field in one IW before the segment is flushed it will not
write anything out. but if for instance in your second IW the last doc in a seg
has a value DV fills it with default values for the other docs. is that
something which could happen here? Same is true if you merge fields ie. if you
have slightly different merge policies?
> DocValues merging is not associative, leading to different results depending
> upon how merges execute
> ----------------------------------------------------------------------------------------------------
>
> Key: LUCENE-3647
> URL: https://issues.apache.org/jira/browse/LUCENE-3647
> Project: Lucene - Java
> Issue Type: Bug
> Affects Versions: 4.0
> Reporter: Robert Muir
> Attachments: LUCENE-3647_multi.patch, LUCENE-3647_test.patch
>
>
> recently I cranked up TestDuelingCodecs to actually test docvalues
> (previously it wasn't testing it at all).
> This test is simple, it indexes the same random content with 2 different
> indexwriters, it just allows them
> to use different codecs with different indexwriterconfigs.
> then it asserts the indexes are equal.
> Sometimes, always on BYTES_FIXED_DEREF type, we end out with one reader that
> has a zero-filled byte[] for a doc,
> but that same document in the other reader has no docvalues at all.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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]
