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>
