[
https://issues.apache.org/jira/browse/SOLR-10047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840577#comment-15840577
]
ASF GitHub Bot commented on SOLR-10047:
---------------------------------------
GitHub user kelaban opened a pull request:
https://github.com/apache/lucene-solr/pull/145
SOLR-10047 - SolrIndexSearcher, UninvertingReader, uninvert docvalues…
… per segment
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kelaban/lucene-solr
jira/master/SOLR-10047/uninverting-reader-per-segment
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/lucene-solr/pull/145.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #145
----
commit 2898c46613f2708ce8c472f821ac4f2c42cd8b48
Author: Keith Laban <[email protected]>
Date: 2017-01-18T21:39:51Z
SOLR-10047 - SolrIndexSearcher, UninvertingReader, uninvert docvalues per
segment
----
> 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
>
> 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.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
