[
https://issues.apache.org/jira/browse/SOLR-10924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16056267#comment-16056267
]
Hoss Man commented on SOLR-10924:
---------------------------------
I've filed this "bug" so we have a record of the discrepency, but personally I
don't think there is anything we should really do to "fix" it. If users are
sending duplicate values to a field and want to dedup just like Trie fields
did, they can use UniqFieldsUpdateProcessorFactory on all numeric fields.
> PointField multivalued docValues don't "dedup" like TrieField
> -------------------------------------------------------------
>
> Key: SOLR-10924
> URL: https://issues.apache.org/jira/browse/SOLR-10924
> 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
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
