lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (SOLR-10924) PointField multivalued docValues don't "dedup" like TrieField
Date Fri, 07 Jul 2017 15:07:00 GMT


ASF subversion and git services commented on SOLR-10924:

Commit 5d1f57f8823e5b6fec5cc617606db6b714c8aaef in lucene-solr's branch refs/heads/master
from Chris Hostetter
[;h=5d1f57f ]

SOLR-10989: Fixup to correct SOLR-11020 test failures (root discrepency caused by SOLR-10924)

> PointField multivalued docValues don't "dedup" like TrieField
> -------------------------------------------------------------
>                 Key: SOLR-10924
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Hoss Man
> As noted by Tomas in SOLR-10835, since the numeric FooPointField classes use SortedNumericDocValues,
the docvalues don't "dedup" when the same value exists multiple times for a single document
-- this is different from the numeric TrieFooField classes that use SortedSetDocValues - which
are by definition a _set_ -- so multiple instances of the same value are de-duplicated.
> This impacts things like the ExportWriter, as well as fields that {{useDocValuesAsStored="true"}}
if users have particular expecations when converting from Trie fields to Point fields.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message