[
https://issues.apache.org/jira/browse/SOLR-3200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13245044#comment-13245044
]
Spyros Kapnissis commented on SOLR-3200:
----------------------------------------
You're welcome:)
Another thing that is not so intuitive here is when using the "all fields"
configuration on a schema that has a unique key defined. This makes the whole
process redundant as deduplication is already covered by the schema's unique
key.
So maybe it would be safe to assume that this configuration always means "all
fields - excluding the unique key" by adding a runtime check to exclude this
field from the signature calculation?
> When using SignatureUpdateProcessor with "all fields" configuration, it will
> assume only the fields present on the very first document only, ignoring any
> optional fields in subsequent documents in the signature generation.
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-3200
> URL: https://issues.apache.org/jira/browse/SOLR-3200
> Project: Solr
> Issue Type: Bug
> Components: update
> Affects Versions: 1.4, 3.1, 3.2, 3.3, 3.4, 3.5, 4.0
> Reporter: Spyros Kapnissis
> Assignee: Hoss Man
> Fix For: 3.6, 4.0
>
> Attachments: SOLR-3200.patch
>
>
> This can result in non-duplicate documents being left out of the index. A
> solution would be that the fields to be used in the signature generation are
> recalculated with every document inserted.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
