You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Spyros Kapnissis (Created) (JIRA)" <ji...@apache.org> on 2012/03/04 11:42:00 UTC
[jira] [Created] (SOLR-3200) 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.
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: 3.5, 4.0
Reporter: Spyros Kapnissis
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Resolved] (SOLR-3200) 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.
Posted by "Hoss Man (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man resolved SOLR-3200.
----------------------------
Resolution: Fixed
Fix Version/s: 4.0
Committed revision 1308625. - 3x
Thank you so much for your patch(es) Spyros
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-3200) 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.
Posted by "Spyros Kapnissis (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Spyros Kapnissis updated SOLR-3200:
-----------------------------------
Attachment: SOLR-3200.patch
I am attaching a patch with the test case and a proposed solution.
> 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: 3.5, 4.0
> Reporter: Spyros Kapnissis
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3200) 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.
Posted by "Hoss Man (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13244800#comment-13244800 ]
Hoss Man commented on SOLR-3200:
--------------------------------
Committed revision 1308604. - trunk
still testing backport to 3x
> 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
>
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3200) 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.
Posted by "Spyros Kapnissis (Commented) (JIRA)" <ji...@apache.org>.
[ 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-3200) 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.
Posted by "Hoss Man (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man updated SOLR-3200:
---------------------------
Affects Version/s: 1.4
3.1
3.2
3.3
3.4
Fix Version/s: 3.6
Assignee: Hoss Man
Grr... another one that looks really bad.
Patch and tests look good to me (but still doing more testing) so I think we should commit for 3.6
(Same upgrade instructions as SOLR-3226 would cover this)
> 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
>
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org