Hey Jay, I understand your concern, and for sure, we will need to keep the current constructors deprecated for a long time (ie, many years).
But if we don't make the move, we will not be able to improve. And I think warnings about using deprecated APIs is an acceptable price to pay. And the API improvements will help new people who adopt Kafka to get started more easily. Otherwise Kafka might end up as many other enterprise software with a lots of old stuff that is kept forever because nobody has the guts to improve/change it. Of course, we can still improve the docs of the deprecated constructors, too. Just my two cents. -Matthias On 4/23/17 3:37 PM, Jay Kreps wrote: > Hey guys, > > I definitely think that the constructors could have been better designed, > but I think given that they're in heavy use I don't think this proposal > will improve things. Deprecating constructors just leaves everyone with > lots of warnings and crossed out things. We can't actually delete the > methods because lots of code needs to be usable across multiple Kafka > versions, right? So we aren't picking between the original approach (worse) > and the new approach (better); what we are proposing is a perpetual > mingling of the original style and the new style with a bunch of deprecated > stuff, which I think is worst of all. > > I'd vote for just documenting the meaning of null in the ProducerRecord > constructor. > > -Jay > > On Wed, Apr 19, 2017 at 3:34 PM, Stephane Maarek < > steph...@simplemachines.com.au> wrote: > >> Hi all, >> >> My first KIP, let me know your thoughts! >> https://cwiki.apache.org/confluence/display/KAFKA/KIP+ >> 141+-+ProducerRecordBuilder+Interface >> >> >> Cheers, >> Stephane >> >
signature.asc
Description: OpenPGP digital signature
