[
https://issues.apache.org/jira/browse/SOLR-10046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15861457#comment-15861457
]
Christine Poerschke commented on SOLR-10046:
--------------------------------------------
Hi Keith,
Thank you for opening this ticket with a pull request.
Thanks also for reviewing and including my suggested
[changes|https://github.com/kelaban/lucene-solr/pull/1] for the lucene part,
the [solr|https://github.com/kelaban/lucene-solr/pull/2] suggestions are
separate just for clarity.
(Split out and linked to this ticket for visibility, LUCENE-7688 and
LUCENE-7689 re: the {{OneMergeWrappingMergePolicy}} location (lucene vs. solr)
and making {{ant documentation-lint}} (part of {{ant recommit}}) pass with it.)
> Create UninvertDocValuesMergePolicy
> -----------------------------------
>
> Key: SOLR-10046
> URL: https://issues.apache.org/jira/browse/SOLR-10046
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Keith Laban
>
> Create a merge policy that can detect schema changes and use
> UninvertingReader to uninvert fields and write docvalues into merged segments
> when a field has docvalues enabled.
> The current behavior is to write null values in the merged segment which can
> lead to data integrity problems when sorting or faceting pending a full
> reindex.
> With this patch it would still be recommended to reindex when adding
> docvalues for performance reasons, as it not guarenteed all segments will be
> merged with docvalues turned on.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
