[
https://issues.apache.org/jira/browse/LUCENE-5189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13768274#comment-13768274
]
Shai Erera commented on LUCENE-5189:
------------------------------------
Jenkins reported this failure, which I'm unable to reproduce with and without
the seed (master and child), with iters.
{noformat}
1 tests failed.
REGRESSION:
org.apache.lucene.index.TestNumericDocValuesUpdates.testManyReopensAndFields
Error Message:
invalid value for doc=351, field=f1 expected:<15> but was:<14>
Stack Trace:
java.lang.AssertionError: invalid value for doc=351, field=f1 expected:<15> but
was:<14>
at
__randomizedtesting.SeedInfo.seed([5E1E0079E35D52E:331D82281FC0B632]:0)
at org.junit.Assert.fail(Assert.java:93)
at org.junit.Assert.failNotEquals(Assert.java:647)
at org.junit.Assert.assertEquals(Assert.java:128)
at org.junit.Assert.assertEquals(Assert.java:472)
at
org.apache.lucene.index.TestNumericDocValuesUpdates.testManyReopensAndFields(TestNumericDocValuesUpdates.java:757)
...
Build Log:
[...truncated 776 lines...]
[junit4] Suite: org.apache.lucene.index.TestNumericDocValuesUpdates
[junit4] 2> NOTE: reproduce with: ant test
-Dtestcase=TestNumericDocValuesUpdates -Dtests.method=testManyReopensAndFields
-Dtests.seed=5E1E0079E35D52E -Dtests.multiplier=3 -Dtests.slow=true
-Dtests.locale=tr -Dtests.timezone=Etc/GMT-6 -Dtests.file.encoding=US-ASCII
[junit4] FAILURE 1.40s J0 |
TestNumericDocValuesUpdates.testManyReopensAndFields <<<
[junit4] > Throwable #1: java.lang.AssertionError: invalid value for
doc=351, field=f1 expected:<15> but was:<14>
[junit4] > at
__randomizedtesting.SeedInfo.seed([5E1E0079E35D52E:331D82281FC0B632]:0)
[junit4] > at
org.apache.lucene.index.TestNumericDocValuesUpdates.testManyReopensAndFields(TestNumericDocValuesUpdates.java:757)
[junit4] > at java.lang.Thread.run(Thread.java:724)
[junit4] 2> NOTE: test params are: codec=Asserting,
sim=RandomSimilarityProvider(queryNorm=false,coord=no): {}, locale=tr,
timezone=Etc/GMT-6
[junit4] 2> NOTE: Linux 3.2.0-53-generic amd64/Oracle Corporation 1.8.0-ea
(64-bit)/cpus=8,threads=1,free=66621176,total=210272256
[junit4] 2> NOTE: All tests run in this JVM: [TestSegmentReader,
TestStressNRT, TestSort, TestShardSearching, TestEliasFanoSequence,
TestBytesRefHash, TestPhrasePrefixQuery, TestLucene45DocValuesFormat,
TestFastCompressionMode, TestEliasFanoDocIdSet, TestSearchForDuplicates,
TestFixedBitSet, TestIsCurrent, TestFilteredSearch,
TestFieldCacheSanityChecker, TestSegmentTermEnum, TestDeletionPolicy,
TestSimpleExplanations, TestRegexpRandom, TestIndexCommit,
TestCloseableThreadLocal, TestNumericRangeQuery32, TestTwoPhaseCommitTool,
TestIndexWriterOnDiskFull, TestPhraseQuery, TestSearchAfter,
TestParallelReaderEmptyIndex, TestMaxTermFrequency,
TestFlushByRamOrCountsPolicy, TestSimilarity, TestNumericRangeQuery64,
TestByteSlices, TestSameScoresWithThreads, TestDocValuesWithThreads,
TestMockAnalyzer, TestArrayUtil, TestPostingsOffsets,
TestCompressingTermVectorsFormat, TestSentinelIntSet, TestCustomNorms,
TestExternalCodecs, TestNumericDocValuesUpdates]
[junit4] Completed on J0 in 83.46s, 24 tests, 1 failure <<< FAILURES!
{noformat}
> Numeric DocValues Updates
> -------------------------
>
> Key: LUCENE-5189
> URL: https://issues.apache.org/jira/browse/LUCENE-5189
> Project: Lucene - Core
> Issue Type: New Feature
> Components: core/index
> Reporter: Shai Erera
> Assignee: Shai Erera
> Attachments: LUCENE-5189.patch, LUCENE-5189.patch, LUCENE-5189.patch,
> LUCENE-5189.patch, LUCENE-5189.patch, LUCENE-5189.patch, LUCENE-5189.patch,
> LUCENE-5189.patch, LUCENE-5189.patch, LUCENE-5189.patch, LUCENE-5189.patch
>
>
> In LUCENE-4258 we started to work on incremental field updates, however the
> amount of changes are immense and hard to follow/consume. The reason is that
> we targeted postings, stored fields, DV etc., all from the get go.
> I'd like to start afresh here, with numeric-dv-field updates only. There are
> a couple of reasons to that:
> * NumericDV fields should be easier to update, if e.g. we write all the
> values of all the documents in a segment for the updated field (similar to
> how livedocs work, and previously norms).
> * It's a fairly contained issue, attempting to handle just one data type to
> update, yet requires many changes to core code which will also be useful for
> updating other data types.
> * It has value in and on itself, and we don't need to allow updating all the
> data types in Lucene at once ... we can do that gradually.
> I have some working patch already which I'll upload next, explaining the
> changes.
--
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]
