You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Hoss Man (Updated) (JIRA)" <ji...@apache.org> on 2012/04/02 21:37:21 UTC
[jira] [Updated] (SOLR-3226) SignatureUpdateProcessor ignores
non-string field values from the signature generation
[ https://issues.apache.org/jira/browse/SOLR-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man updated SOLR-3226:
---------------------------
Attachment: SOLR-3226.patch
Hmmm .... just noticed this jira ... this definitely seems like a really bad bug.
Spyros: thank you so much for your patch (including tests!) ... i've updated it to also fix the case of Collections that contain non string.
> SignatureUpdateProcessor ignores non-string field values from the signature generation
> --------------------------------------------------------------------------------------
>
> Key: SOLR-3226
> URL: https://issues.apache.org/jira/browse/SOLR-3226
> Project: Solr
> Issue Type: Bug
> Components: update
> Affects Versions: 3.5, 4.0
> Reporter: Spyros Kapnissis
> Attachments: SOLR-3226.patch, SOLR-3226.patch
>
>
> When using for example XMLUpdateRequestProcessor, the signature is calculated correctly since all field values are strings. But when one uses DataImportHandler or BinaryUpdateRequestHandler, the signature generation will ignore any field values that are ints, longs, dates etc.
> This might result in overwriting non-similar documents, as it happened in my case while importing some db data through DIH.
--
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org