[
https://issues.apache.org/jira/browse/SOLR-10047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15979028#comment-15979028
]
Hoss Man commented on SOLR-10047:
---------------------------------
MergePolicy settings are normally randomized by the solr test configs.
If a test is dependent on controlling exact when a merge does/doesn't happen,
you'll need to force the mergepolicy using something like
{{NoMergePolicyFactory}}
Example from TestInPlaceUpdatesDistrib...
{code}
// we need consistent segments that aren't re-ordered on merge because we're
// asserting inplace updates happen by checking the internal [docid]
systemSetPropertySolrTestsMergePolicyFactory(NoMergePolicyFactory.class.getName());
// HACK: Don't use a RandomMergePolicy, but only use the mergePolicyFactory
that we've just set
System.setProperty(SYSTEM_PROPERTY_SOLR_TESTS_USEMERGEPOLICYFACTORY, "true");
System.setProperty(SYSTEM_PROPERTY_SOLR_TESTS_USEMERGEPOLICY, "false");
{code}
(the last two lines are only needed because we're phasing out MergePolicy for
MergePolicyFactory)
> 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
