lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Jelsma (JIRA)" <>
Subject [jira] [Updated] (SOLR-3473) Distributed deduplication broken
Date Mon, 06 Aug 2012 10:21:02 GMT


Markus Jelsma updated SOLR-3473:

    Attachment: SOLR-3473-trunk-2.patch

Hello - Could the deleteByQuery issue you mention be fixed with SOLR-3473? I've attached an
updated patch for today's trunk. The previous patch was missing the signature field but i
added it to one schema. Now other tests seem to fail because they don't see the sig field
but do use the update chain.

Anyway, it seems the BasicDistributedZkTest passes but i'm not very sure, there's too much
log output but it doesn't fail.
> Distributed deduplication broken
> --------------------------------
>                 Key: SOLR-3473
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud, update
>    Affects Versions: 4.0-ALPHA
>            Reporter: Markus Jelsma
>             Fix For: 4.0
>         Attachments: SOLR-3473-trunk-2.patch, SOLR-3473.patch, SOLR-3473.patch
> Solr's deduplication via the SignatureUpdateProcessor is broken for distributed updates
on SolrCloud.
> Mark Miller:
> {quote}
> Looking again at the SignatureUpdateProcessor code, I think that indeed this won't currently
work with distrib updates. Could you file a JIRA issue for that? The problem is that we convert
update commands into solr documents - and that can cause a loss of info if an update proc
modifies the update command.
> I think the reason that you see a multiple values error when you try the other order
is because of the lack of a document clone (the other issue I mentioned a few emails back).
Addressing that won't solve your issue though - we have to come up with a way to propagate
the currently lost info on the update command.
> {quote}
> Please see the ML thread for the full discussion:

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


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

View raw message