This summary is correct. If you are just starting development now it is
probably reasonable to start with the new producer. We would certainly
appreciate any feedback on it.
My recommendation would be to build the producer off trunk as there were a
few bug fixes since 0.8.1.x that are worth gettin
Hi Christian,
As Jun mentioned, the new producer is marked beta since it is new. By 0.9
or even sooner, we'd expect it to be deployed at LinkedIn and a few other
companies in a stable state. The APIs, guarantees and features will not
change by 0.9, just the stability.
Thanks,
Neha
On Fri, May 2
It's beta mostly because it's new.
Thanks,
Jun
On Thu, May 1, 2014 at 10:25 PM, cac...@gmail.com wrote:
> Thanks, that's quite helpful. According to this post,
> http://blog.empathybox.com/ , it looks like it will be beta then which
> seems good enough. Assuming that the beta designation is c
Thanks, that's quite helpful. According to this post,
http://blog.empathybox.com/ , it looks like it will be beta then which
seems good enough. Assuming that the beta designation is correct, is that
because it won't have as many features/the same flexibility as it's
expected to by 0.9?
Christian
The javadoc of the new producer is here for now -
http://empathybox.com/kafka-javadoc/index.html?kafka/clients/producer/KafkaProducer.html
Thanks,
Neha
On Thu, May 1, 2014 at 9:16 PM, Jun Rao wrote:
> The new producer (that supports callbacks) is in trunk. It will be released
> in 0.8.2. You c
The new producer (that supports callbacks) is in trunk. It will be released
in 0.8.2. You can look at the java doc of KafkaProducer for the api.
Thanks
Jun
On Thu, May 1, 2014 at 8:43 PM, Christian Csar wrote:
> On 05/01/2014 07:22 PM, Christian Csar wrote:
> > I'm looking at using the java p
On 05/01/2014 07:22 PM, Christian Csar wrote:
> I'm looking at using the java producer api for 0.8.1 and I'm slightly
> confused by this passage from section 4.4 of
> https://kafka.apache.org/documentation.html#theproducer
> "Note that as of Kafka 0.8.1 the async producer does not have a
> callback