: DistributedUpdateProcessor (or what I call DURP for short) is very : complex. One aspect of the complexity is that it appears it tries to : support SolrCloud and classic Solr. Do we still need it to support classic : Solr? When/why? Forever?
Part of the issue here is that DUP is responsible for applying atomic update operations regardless of wehter here is any actual "distribtued" updating happening -- because it has to be in cloud mode in order to ensure the atomic updates happen exactly once on the leader. that's the fundemental reason the UpdateProcessorChain can't just "optmize away" the need for DUP in non-cloud use cases and let the DUP internals just assert "zkEnabled" in all cases As far as the broader question of: "Do we still need it to support classic Solr? When/why? Forever?" ... that feels like a much more significant question that warrants it's own thread/jira with a very clear subject since it's a much bigger/broader topic of cnversation (with a much greater impact on user experience) then just a dicussion of the (internal) complexity involved in DistributedUpdateProcessor. -Hoss http://www.lucidworks.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
