-1. The amount of changes this will need, especially around tools and code developed around the old API is enormous.
And no, remaining with the old lib is not an option, unless there is a plan to maintain the old lib, with dependencies up-to-date with security fixes I would like the team to discuss and publish a clear plan around LTS for Pulsar, not only just the API, but also BK. Joe On Thu, Dec 13, 2018 at 11:18 AM Matteo Merli <mme...@apache.org> wrote: > When Pulsar 2.0.x was released we have marked some parts of the client APIs > as deprecated. The main driver was to accommodate the new typed API and > integration with the schema registry. > > Examples: > > http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ProducerConfiguration.html > > With this proposal: > * Pulsar 2.4 client will not have the deprecated APIs > * Applications can still use older client library when talking to newer > Pulsar service > > This cleanup will help in avoid confusion in users and reduce the "API" > surface that is currently filled with basically 2 versions of most > operations. > > Any thoughts / concerns? > > > -- > Matteo Merli > <mme...@apache.org> >
