This makes much more sense to me. +1
> On Jun 1, 2017, at 10:33 AM, Kyle Winkelman wrote:
>
> I have updated the KIP and my PR. Let me know what you think.
> To created a cogrouped stream just call cogroup on a KgroupedStream and
> supply the initializer, aggValueSerde, and an aggregator. Then c
> On Jun 2, 2017, at 12:54 AM, Matthias J. Sax wrote:
>
> With regard to backward compatibility, we should not change the current
> interface, but add a new interface that extends the current one.
>
++1
For account: Jim Jagielski (j...@jagunet.com) : jimjag
tia
[
https://issues.apache.org/jira/browse/KAFKA-4566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16032048#comment-16032048
]
Jim Jagielski commented on KAFKA-4566:
--
Since this is a shell, we can check whic
+1
> On May 27, 2017, at 9:27 PM, Vahid S Hashemian
> wrote:
>
> Sure, that sounds good.
>
> I suggested that to keep command line behavior consistent.
> Plus, removal of ACL access is something that can be easily undone, but
> topic deletion is not reversible.
> So, perhaps a new follow-up JI
> On May 26, 2017, at 1:10 PM, Vahid S Hashemian
> wrote:
>
> Gwen, thanks for the KIP.
> It looks good to me.
>
> Just a minor suggestion: It would be great if the command asks for a
> confirmation (y/n) before deleting the topic (similar to how removing ACLs
> works).
>
+1 (or some sort
> On May 26, 2017, at 5:13 AM, Eno Thereska wrote:
>
>
>>
>>
>> With regard to `DeserializationException`, do you thing it might make
>> sense to have a "dead letter queue" as a feature to provide out-of-the-box?
>
> We could provide a special topic where bad messages go to, and then we'd ha
+1
> On Nov 30, 2016, at 4:34 PM, Xavier Léauté wrote:
>
> Based on the feedback KIP-96 seems pretty uncontroversial, so I'd like to
> initiate a vote on it.
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-96+-+Add+per+partition+metrics+for+in-sync+and+assigned+replica+count
>
> Xavie
+1!
> On Oct 26, 2016, at 11:26 AM, Rajini Sivaram
> wrote:
>
> I would like to initiate the voting process for KIP-85: Dynamic JAAS
> configuration for Kafka Clients:
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-85%3A+Dynamic+JAAS+configuration+for+Kafka+clients
>
> This KIP ena
++1
> On Oct 21, 2016, at 11:47 AM, Gwen Shapira wrote:
>
> I think this will be a good idea. It will separate an issue with concrete
> use-case and a major pain-point from a wider discussion about architectures
> and who is responsible for data formats.
>
>
> On Fri, Oct 21, 2016 at 12:57 AM,
Yeah, let's figure out the "best" action to take...
Looks like something I'd like to get a handle on.
> On Aug 31, 2016, at 4:05 PM, Jason Gustafson wrote:
>
> Hi Achintya,
>
> We have a JIRA for this problem: https://issues.
> apache.org/jira/browse/KAFKA-3834. Do you expect the client to rai
t; On Wed, Aug 31, 2016 at 5:19 PM, Jim Jagielski wrote:
>
>> Just a reminder that these kinds of meetings are, by their very nature,
>> synchronous and disenfranchise those members of the community unable to
>> attend.
>>
>> It is great that discussions and vid
+1
> On Aug 25, 2016, at 6:57 AM, Eno Thereska wrote:
>
> Hi folks,
>
> We'd like to start the vote for KIP-63. At this point the Wiki addresses
> all previous questions and we believe the PoC is feature-complete.
>
> Thanks
> Eno
Just a reminder that these kinds of meetings are, by their very nature,
synchronous and disenfranchise those members of the community unable to
attend.
It is great that discussions and videos are brought back to the
list BUT they should not be "this is what has been decided" or
"this is what we ar
+1
> On Aug 29, 2016, at 5:50 AM, Matthias J. Sax wrote:
>
> I’d like to initiate the voting process for KIP-77:
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-77%3A+Improve+Kafka+Streams+Join+Semantics
>
> -Matthias
>
>
> long experience in Apache :)
>
> Gwen
>
> On Tue, Aug 16, 2016 at 6:59 AM, Jim Jagielski wrote:
>> By being aware of the potential issues, it's easier to address
>> them at the start, and to create a process which does what
>> it can to "ensure" t
way.
>
> Ismael
>
> On Tue, Aug 16, 2016 at 2:42 PM, Jim Jagielski wrote:
>
>> The idea of time-based releases make sense. The issue is
>> when they become the tail wagging the dog.
>>
>> Recall that all developers and contributors are assumed to
>
The idea of time-based releases make sense. The issue is
when they become the tail wagging the dog.
Recall that all developers and contributors are assumed to
be doing this because they are personally invested in the
project. Their is also the assumption that, as such, they
are volunteers and do t
Looks good here: +1
> On Aug 4, 2016, at 9:54 AM, Ismael Juma wrote:
>
> Hello Kafka users, developers and client-developers,
>
> This is the third candidate for the release of Apache Kafka 0.10.0.1. This
> is a bug fix release and it includes fixes and improvements from 53 JIRAs
> (including a
[
https://issues.apache.org/jira/browse/KAFKA-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15407632#comment-15407632
]
Jim Jagielski commented on KAFKA-3940:
--
Could you send over the patch... either
> On Jul 21, 2016, at 10:57 PM, Ismael Juma wrote:
>
> Hi Grant,
>
> Thanks for the KIP. A few questions and comments:
>
> 1. My main concern is that we are skipping the discussion on the desired
> model for controlling ACL access and updates. I understand the desire to
> reduce the scope, bu
[
https://issues.apache.org/jira/browse/KAFKA-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382927#comment-15382927
]
Jim Jagielski commented on KAFKA-3940:
--
Let me know if I can add myself to
Very cool.
> On Jul 16, 2016, at 9:55 AM, Damian Guy wrote:
>
> Hi,
> The vote is now complete and KIP-67 has been accepted and adopted.
> Thanks everyone for the input etc.
>
> Regards,
> Damian
>
> On Sat, 16 Jul 2016 at 06:53 Damian Guy wrote:
>
>> Hi,
>> Jay's interpretation is correct.
[
https://issues.apache.org/jira/browse/KAFKA-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378180#comment-15378180
]
Jim Jagielski commented on KAFKA-3940:
--
In some places we do a dir.mkdirs()
[
https://issues.apache.org/jira/browse/KAFKA-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378153#comment-15378153
]
Jim Jagielski commented on KAFKA-3940:
--
I'm fine w/ working w/ Ishita... W
tate, it
>>> appears to me that a majority would just use the key value store. Partly
>>> because that will suffice and partly because people might just follow the
>>> simpler examples we provide that use key-value store. For advanced users,
>>> they will be awa
[
https://issues.apache.org/jira/browse/KAFKA-3940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15375225#comment-15375225
]
Jim Jagielski commented on KAFKA-3940:
--
Pull request created
> Log should ch
IMO, that makes the most sense.
> On Jul 12, 2016, at 5:11 PM, Ismael Juma wrote:
>
> Hi Damian,
>
> How about StreamsMetadata instead? The general naming pattern seems to
> avoid the `Kafka` prefix for everything outside of `KafkaStreams` itself.
>
> Ismael
>
> On Tue, Jul 12, 2016 at 7:14 P
28 matches
Mail list logo
