HI Jay,
I am running trunk producer based on following last commit with timestamp
Mon Sep 15 20:34:14 2014 -0700. Please let me know if this timestamp
contains the fix. Otherwise, I will file a bug with logs as Neha suggested.
commit cf0f5750b39e675cf9a9c6d6394a665366db0f58
Author: Alexis Midon
Good to know. Does it mean release will go out after those bug is fixed or
moved to newer release? :)
Best Regards,
Mingtao
On Wed, Sep 17, 2014 at 9:34 PM, Neha Narkhede
wrote:
> You can track the list of open bugs here
> <
> https://issues.apache.org/jira/browse/KAFKA-1558?jql=project%20%3D%2
Hi Mingtao,
We are shooting to cut the 0.8.2 branch this month.
Guozhang
On Thu, Sep 18, 2014 at 10:36 AM, Mingtao Zhang
wrote:
> Good to know. Does it mean release will go out after those bug is fixed or
> moved to newer release? :)
>
> Best Regards,
> Mingtao
>
> On Wed, Sep 17, 2014 at 9:34
Great :)
Best Regards,
Mingtao
On Thu, Sep 18, 2014 at 2:04 PM, Guozhang Wang wrote:
> Hi Mingtao,
>
> We are shooting to cut the 0.8.2 branch this month.
>
> Guozhang
>
> On Thu, Sep 18, 2014 at 10:36 AM, Mingtao Zhang
> wrote:
>
> > Good to know. Does it mean release will go out after those
Otis,
In kafka-1481, we will have to change the mbean names (at least the ones
with clientid and topic) anyway. Using the name/value pair in the mbean
name allows us to do this in a cleaner way. Yes, "," is not allowed in
clientid or topic.
Bhavesh,
Yes, I was thinking of making changes in the n
Hello all!
I'm curious about the interaction of server and topic level retention
settings. It's not clear to me the precedence of the follow:
- broker's default log.retention.bytes
- topic's retention.bytes (which defaults to broker's
log.retention.bytes)
- broker's log.retention.hour
Hmm, yes, the fix was prior to that, that sounds like a bug.
-Jay
On Thu, Sep 18, 2014 at 9:39 AM, Bhavesh Mistry
wrote:
> HI Jay,
>
> I am running trunk producer based on following last commit with timestamp
> Mon Sep 15 20:34:14 2014 -0700. Please let me know if this timestamp
> contains the
Hey Jae,
The rationale for switching was to use a hash code that is cross
language and not dependent on the particular object. There are all
kinds of gotchas with Java's hashCode() as a partition assignment
strategy (e.g. two byte arrays with the same bytes will have different
hash codes).
-Jay
I am trying to understand the best practices for working with the new
(0.8.2) Producer interface.
We have a process in a large server that writes a lot of data to Kafka.
However, this data is not mission critical. When a problem arises writing
to Kafka, most specifically network issues, but also f
