On Fri, Apr 5, 2024 at 8:52 AM Ilan Ginzburg wrote:
>
> I would suggest doing any such change in two independent steps:
> - Moving classes around without any functional change ("pure" refactoring)
> - A change to what a class exposes, its behavior etc.
> Otherwise it is very hard to track what
I would suggest doing any such change in two independent steps:
- Moving classes around without any functional change ("pure" refactoring)
- A change to what a class exposes, its behavior etc.
Otherwise it is very hard to track what has simply moved and what has
changed.
Is the principal
I've been looking at HttpClusterStateProvider lately, and of ClusterState.
It has a method getClusterState which goes and loads the complete
ClusterState (all collections with all state info). ClusterState is
immutable. At a massive collection scale, such a method is very
disconcerting!
