On Thu, Dec 13, 2018 at 11:29 AM Joe Francis wrote:
> -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 dependen
-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 dis
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
