On Mon, Jul 24, 2017 at 5:22 AM, Enrico Olivelli <[email protected]> wrote:
> Hi, > we are going to release 4.5 soon, in this release we changed > EnsemblePlacementPolicy interface. > > It you are using a "custom" EnsemblePlacementPolicy in 4.4 and you just > switch the bookeeeper-server JAR on the classpath your application won't > run. > > I already got that problem and I needed to implement some "support 4.5" > option in my projects which essentially tells "do not use a custom policy", > this is very bad because there is no way to apply the custom rules required > by the project. > Do you mean the new methods introduced in placement policy? Or methods that whose signatures are changed? I believe the new methods 'reorderSequence' is disabled by default unless you enable it explicitly. For methods that whose signatures were changed, we can add the old methods back and create overrides to keep the binary backward compatible. However I am not sure if this works because the placement policy is instantiated and loaded by reflection. Typically when you upgrade a version, you have to compile it first, no? > > As we are going to break the API now, would it be good to create a more > future-proof API ? We can just post-pone the problem to 4.6 > > Thoughts ? > > Enrico >
