[
https://issues.apache.org/jira/browse/SOLR-10047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974706#comment-15974706
]
Steve Rowe commented on SOLR-10047:
-----------------------------------
Policeman Jenkins failure reproduces for me
[https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/19429/]:
{noformat}
Checking out Revision 48d54ac45860a1b75bfd79aaffe9d4d24c2ad5a8
(refs/remotes/origin/master)
[...]
[junit4] 2> NOTE: reproduce with: ant test -Dtestcase=DocValuesTest
-Dtests.method=testHalfAndHalfDocValues -Dtests.seed=D4C321F7B9F8C0F3
-Dtests.multiplier=3 -Dtests.slow=true -Dtests.locale=hu-HU
-Dtests.timezone=WET -Dtests.asserts=true -Dtests.file.encoding=UTF-8
[junit4] FAILURE 0.04s J1 | DocValuesTest.testHalfAndHalfDocValues <<<
[junit4] > Throwable #1: java.lang.AssertionError: expected:<3> but
was:<2>
[junit4] > at
__randomizedtesting.SeedInfo.seed([D4C321F7B9F8C0F3:1B0859436D75536E]:0)
[junit4] > at
org.apache.solr.schema.DocValuesTest.testHalfAndHalfDocValues(DocValuesTest.java:192)
[...]
[junit4] 2> NOTE: test params are: codec=Asserting(Lucene70),
sim=RandomSimilarity(queryNorm=false): {}, locale=hu-HU, timezone=WET
[junit4] 2> NOTE: Linux 4.4.0-72-generic i386/Oracle Corporation 1.8.0_121
(32-bit)/cpus=12,threads=1,free=146280496,total=518979584
{noformat}
When I run the repro line on my Linux box, the actual value was {{1}} instead
of the {{2}} though, so at a minimum there's some flakiness here:
{{[junit4] > Throwable #1: java.lang.AssertionError: expected:<3> but
was:<1>}}
> Mismatched Docvalue segments cause exception in Sorting/Facting; Uninvert per
> segment
> -------------------------------------------------------------------------------------
>
> Key: SOLR-10047
> URL: https://issues.apache.org/jira/browse/SOLR-10047
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Keith Laban
> Assignee: Shalin Shekhar Mangar
> Fix For: 6.6, master (7.0)
>
>
> The configuration of UninvertingReader in SolrIndexSearch creates a global
> mapping for the directory for fields to uninvert. If docvalues are enabled on
> a field the creation of a new segment will cause the query to fail when
> faceting/sorting on the recently docvalue enabled field. This happens because
> the UninvertingReader is configured globally across the entire directory, and
> a single segment containing DVs for a field will incorrectly indicate that
> all segments contain DVs.
> This patch addresses the incorrect behavior by determining the fields to be
> uninverted on a per-segment basis.
> With the fix, it is still recommended that a reindexing occur as data loss
> will when a DV and non-DV segment are merged, SOLR-10046 addresses this
> behavior. This fix is to be a stop gap for the time between enabling
> docvalues and the duration of a reindex.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
