[ https://issues.apache.org/jira/browse/SOLR-10046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15948991#comment-15948991 ]
ASF subversion and git services commented on SOLR-10046: -------------------------------------------------------- Commit 4d3e94befcb5ea361ceff1fcff1bdc3e6166fdf1 in lucene-solr's branch refs/heads/branch_6_5 from [~cpoerschke] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=4d3e94b ] SOLR-10046: remove CHANGES.txt entry (Reverses unintentional add alongside SOLR-10085 and SOLR-10254 CHANGES.txt update.) > 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 > Assignee: Christine Poerschke > > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org