Hoss: Thanks very much for your insight! Hmmm; this seems tractable. It
could probably be addressed with a "urp phase" enum of sorts... and then
splitting the DURP into some pieces that honor certain phases. I'm just
thinking out loud here... I don't think I have time to undertake a large
refact
: 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
I wish that we only had one Solr mode as well. We now have features that only
work in SolrCloud mode, like the SQL handler…. For a very small 1000 document
set up, I recently deployed it as a single node single shard no replica
SolrCloud setup using embedded ZK, just to take advantage of the
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?
If it needs to continue to operate in both modes, perhaps
