[
https://issues.apache.org/jira/browse/SOLR-12955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16675554#comment-16675554
]
Shawn Heisey commented on SOLR-12955:
-------------------------------------
My only real concern is how existing configs are handled.
What happens if somebody upgrades a Solr where DistributedUpdateProcessor is
being used in their config? Will it continue to work as before and just log a
deprecation warning? If they upgrade to a new major version and don't change to
the appropriate new class, would their core(s) fail to start? Those two
courses of action would be IMHO the best way to go.
> Refactor DistributedUpdateProcessor
> -----------------------------------
>
> Key: SOLR-12955
> URL: https://issues.apache.org/jira/browse/SOLR-12955
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Bar Rotstein
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Lately As I was skimming through Solr's code base I noticed that
> DistributedUpdateProcessor has a lot of nested if else statements, which
> hampers code readability.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
