[VOTE] Pulsar Release 2.2.1 Candidate 1

2018-12-13 Thread Matteo Merli
This is the first release candidate for Apache Pulsar, version 2.2.1. It fixes the following issues: https://github.com/apache/pulsar/milestone/19?closed=1 *** Please download, test and vote on this release. This vote will stay open for at least 72 hours *** Note that we are voting upon the sour

Re: [PROPOSAL] Remove deprecated client APIs in 2.4 release

2018-12-13 Thread Matteo Merli
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

Re: [PROPOSAL] Remove deprecated client APIs in 2.4 release

2018-12-13 Thread Joe Francis
-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

[PROPOSAL] Remove deprecated client APIs in 2.4 release

2018-12-13 Thread Matteo Merli
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

Re: Planning to kickoff 2.2.1 release

2018-12-13 Thread Sanjeev Kulkarni
+1 On Wed, Dec 12, 2018 at 4:02 PM Matteo Merli wrote: > We have accumulated a fair amount of fixes after 2.2.0 release. > > https://github.com/apache/pulsar/milestone/19?closed=1 > > One of the requirements was to have BookKeeper 4.7.3 which is now available > so I would recommend that we proce