Thanks, Neha. Sorry for the confusion.
Best,
Rob
> On Sep 25, 2014, at 11:24 AM, Neha Narkhede wrote:
>
> No. But there is a good chance that it will be available in 0.8.2
>
> On Thu, Sep 25, 2014 at 8:08 AM, Robert Withers
> wrote:
>
>> Is that in 0.8.0.0?
>>
>> - Rob
Is that in 0.8.0.0?
- Rob
Just never mind.
heart beat and you need a new commit notification
> message. I think that would make this proposal more complex than the
> current one.
>
> -Jay
>
> On Mon, Jul 21, 2014 at 6:44 PM, Robert Withers
> wrote:
>> Thanks, Jay, for the good summary. Regarding point 2, I wo
...live assignments! :)
> On Jul 21, 2014, at 7:44 PM, Robert Withers
> wrote:
>
> Thanks, Jay, for the good summary. Regarding point 2, I would think the
> heartbeat would still be desired, to give control over liveness detection
> parameters and to directly inform cl
ebalance process even
>> with a global barrier should usually be very fast, with a few hundreds of
>> millis. So I am not sure if this is a worthy optimization that we would
>> want for now. What do you think?
>>
>> Guozhang
>>
>>
>> On Sat, Jul 1
rix?
>
> That's neat, thank you for Kafka!
>
> Rob
>
>> On Friday, July 18, 2014 at 7:22 PM, Robert Withers
>> wrote:
>>
>> I had some time to consider my suggestion that it be viewed
>> as a relativistic frame of reference.
e new guy, so it lags a
bit. Do you think this could this work?
Thanks,
Rob
> On Jul 18, 2014, at 7:22 PM, Robert Withers
> wrote:
>
> Hi Guozhang,
>
> Thank you for considering my suggestions. The security layer sounds like the
> right facet to design for these sorts
nk of it as relativistic from each acceleration
>> frame of reference, which is each consumer: event horizons.
>>
>>
>>
>> Regards,
>>
>> Rob
>>
>>
>>
>>
>>
>> -Original Message-
>> From: Guozha
> On Jul 14, 2014, at 3:20 PM, Baran Nohutçuoğlu wrote:
>
>
>> On Jul 8, 2014, at 3:17 PM, Guozhang Wang wrote:
>>
>> Hi All,
>>
>> We have written a wiki a few weeks back proposing a single-threaded ZK-free
>> consumer client design for 0.9:
>>
>> https://cwiki.apache.org/confluence/displa
f the message, but rather a separate structure entirely that is
> stored with the message).
>
> -Todd
>
>> On 6/10/14, 3:26 PM, "Robert Withers" wrote:
>>
>> What strikes me as an opportunity is to define a plug gable at-rest
>> encryption module i
e it that way and keep the key pair and session key
> handling simple. The more we can do that, the more we can leave key
> management as a separate component that can be swapped out so the user can
> decide how it should be done.
>
> -Todd
>
>
>> On 6/9/14, 8:16 AM, &qu
Yes, that sounds familiar as I helped write (minimally) S/MIME in squeak (open
source Smalltalk environment). This what I was thinking in my alternative
here, though I have a concern...
Production may occur before the consumer is coded and executed. In the analogy
of mail, the mail is sent be
It would be nice to have Alcatraz on-disk security for the discriminating
client.
Thanks,
Rob
> On Jun 6, 2014, at 11:51 AM, Pradeep Gollakota wrote:
>
> I'm actually not convinced that encryption needs to be handled server side
> in Kafka. I think the best solution for encryption is to handle
>>> The use of the callbacks is explained in the javadoc here -
>>>
>> http://people.apache.org/~nehanarkhede/kafka-0.9-consumer-javadoc/doc/kafka/clients/consumer/ConsumerRebalanceCallback.html
>>>
>>> Let me know if it makes sense. Th
t makes sense. The hope is to improve the javadoc so that
> it is self explanatory.
>
> Thanks,
> Neha
>
>
> On Wed, Feb 26, 2014 at 9:16 AM, Robert Withers
> wrote:
>
>> Neha, what does the use of the RebalanceBeginCallback and
>> RebalanceEndCallback look
partitions.
>>>>>>
>>>>>> 4. There is inconsistency in specifying partitions. Sometimes we use
>>>>>> TopicPartition and some other times we use String and int (see
>>>>>> examples below).
>>>>>>
>>>>>> void onPartitionsAs
ng
> you to be more failure tolerant on the consuming side.
>
>
> On Sat, Feb 15, 2014 at 12:46 PM, Robert Withers > wrote:
>
>> We have this version in prod. It has been fine as we commitOffsets after
>> every message. After 3 months of this, we rolled out Hadoop, whi
We have this version in prod. It has been fine as we commitOffsets after every
message. After 3 months of this, we rolled out Hadoop, which requires
aggregation. We started commiting every 2 minutes and we saw that the fetchr
would get tangled and stop fetching and the consumer would get stuc
19 matches
Mail list logo