Re: Like to contribute

Sunitha, Kafka Connect and Kafka Stream are both written in Java. If you want to get started, look for Jira with label "beginner" or similar. Also have a look here: https://cwiki.apache.org/confluence/display/KAFKA/Contributing+Code+Changes Let us know if you have further question. Welcome to

Re: [VOTE] KIP-123: Allow per stream/table timestamp extractor

+1 Thanks a lot for the KIP! -Matthias On 2/28/17 1:35 AM, Damian Guy wrote: > Thanks for the KIP Jeyhun! > > +1 > > On Tue, 28 Feb 2017 at 08:59 Jeyhun Karimov wrote: > >> Dear community, >> >> I'd like to start the vote for KIP-123: >>

Re: [DISCUSS] KIP-123: Allow per stream/table timestamp extractor

Eno, I think this problem is out-of-scope and also present in the current setting. We cannot avoid that a custom timestamp extractor uses and if-else branch and returns different timestamps for different topic. That is possible even right now. Furthermore, the TimestampExtractor interface

Re: [VOTE] KIP-119: Drop Support for Scala 2.10 in Kafka 0.11

＋1 On Tue, Feb 28, 2017 at 4:28 AM, Tom Crayford wrote: > +1 (non-binding) > > On Tue, 28 Feb 2017 at 11:42, Molnár Bálint > wrote: > > > +1 > > > > 2017-02-28 12:17 GMT+01:00 Dongjin Lee : > > > > > > > > > > > +1. > > > > > >

[jira] [Updated] (KAFKA-4814) ZookeeperLeaderElector not respecting zookeeper.set.acl

[ https://issues.apache.org/jira/browse/KAFKA-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4814: --- Priority: Major (was: Minor) > ZookeeperLeaderElector not respecting zookeeper.set.acl >

[jira] [Updated] (KAFKA-4814) ZookeeperLeaderElector not respecting zookeeper.set.acl

[ https://issues.apache.org/jira/browse/KAFKA-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4814: --- Fix Version/s: 0.10.2.1 0.10.3.0 > ZookeeperLeaderElector not respecting

[jira] [Updated] (KAFKA-4814) ZookeeperLeaderElector not respecting zookeeper.set.acl

[ https://issues.apache.org/jira/browse/KAFKA-4814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4814: --- Labels: newbie (was: ) > ZookeeperLeaderElector not respecting zookeeper.set.acl >

[jira] [Created] (KAFKA-4814) ZookeeperLeaderElector not respecting zookeeper.set.acl

Stevo Slavic created KAFKA-4814: --- Summary: ZookeeperLeaderElector not respecting zookeeper.set.acl Key: KAFKA-4814 URL: https://issues.apache.org/jira/browse/KAFKA-4814 Project: Kafka Issue

[jira] [Commented] (KAFKA-4811) ReplicaFetchThread may fail to create due to existing metric

[ https://issues.apache.org/jira/browse/KAFKA-4811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15888339#comment-15888339 ] Jun Rao commented on KAFKA-4811: [~huxi_2b], yes, we should check both host and port and recreate the

Like to contribute

Hi I have been using for a while now and would like to be a contributor. I am a core java developer. May I know which part of kafka is written in java? as it is also written in Scala.. Would you please help me pick up some jira and add me to contributor list? thanks Sunitha

Re: [DISCUSS] KIP-123: Allow per stream/table timestamp extractor

Hi Eno, Thanks for clarification. I think it is by definition allowed. So if we want to join a stream that uses wallclock time with a stream that uses an event time, then we can assign the first one a timestamp extractor that returns system clock, and for the second stream we can assign

[jira] [Commented] (KAFKA-4677) Avoid unnecessary task movement across threads during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-4677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15888161#comment-15888161 ] ASF GitHub Bot commented on KAFKA-4677: --- GitHub user dguy opened a pull request:

[GitHub] kafka pull request #2609: KAFKA-4677: [Follow Up] add optimization to Sticky...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/2609 KAFKA-4677: [Follow Up] add optimization to StickyTaskAssignor for rolling rebounce Detect when a rebalance has happened due to one or more existing nodes bouncing. Keep assignment of previous active

[jira] [Commented] (KAFKA-4669) KafkaProducer.flush hangs when NetworkClient.handleCompletedReceives throws exception

[ https://issues.apache.org/jira/browse/KAFKA-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15888126#comment-15888126 ] Federico Giraud commented on KAFKA-4669: We had the same issue with a Kafka 0.8.2.0 producer and a

Re: [DISCUSS] 0.10.3.0/0.11.0.0 release planning

Thanks Ismael, +1 for 0.11.0.0 2017-02-28 15:20 GMT+01:00 Ofir Manor : > Thanks Ismael, makes perfect sense :) > > Ofir Manor > > Co-Founder & CTO | Equalum > > Mobile: +972-54-7801286 | Email: ofir.ma...@equalum.io > > On Tue, Feb 28, 2017 at 1:02 PM, Ismael Juma

Re: [DISCUSS] 0.10.3.0/0.11.0.0 release planning

Thanks Ismael, makes perfect sense :) Ofir Manor Co-Founder & CTO | Equalum Mobile: +972-54-7801286 | Email: ofir.ma...@equalum.io On Tue, Feb 28, 2017 at 1:02 PM, Ismael Juma wrote: > Hi Ofir, > > Thanks for the feedback. This will be the first release with exactly-once.

[jira] [Created] (KAFKA-4813) 2h6R1

Vamsi Jakkula created KAFKA-4813: Summary: 2h6R1 Key: KAFKA-4813 URL: https://issues.apache.org/jira/browse/KAFKA-4813 Project: Kafka Issue Type: Bug Reporter: Vamsi Jakkula

[jira] [Commented] (KAFKA-4779) Failure in kafka/tests/kafkatest/tests/core/security_rolling_upgrade_test.py

[ https://issues.apache.org/jira/browse/KAFKA-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15887978#comment-15887978 ] ASF GitHub Bot commented on KAFKA-4779: --- GitHub user rajinisivaram opened a pull request:

[GitHub] kafka pull request #2608: KAFKA-4779: Request metadata in consumer if partit...

GitHub user rajinisivaram opened a pull request: https://github.com/apache/kafka/pull/2608 KAFKA-4779: Request metadata in consumer if partitions unavailable If leader node of one more more partitions in a consumer subscription are temporarily unavailable, request metadata refresh

Re: [VOTE] KIP-123: Allow per stream/table timestamp extractor

That's ok, that was my fault for looking at this thread late. We can leave the vote thread as is and simultaneously answer any remaining questions on the discuss thread. Thanks Eno > On 28 Feb 2017, at 12:55, Michael Noll wrote: > > Thanks, Jeyhun! > > I observed that

[jira] [Commented] (KAFKA-3990) Kafka New Producer may raise an OutOfMemoryError

[ https://issues.apache.org/jira/browse/KAFKA-3990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15887957#comment-15887957 ] Adrian McCague commented on KAFKA-3990: --- I have narrowed down my particular issues to being caused

Re: [VOTE] KIP-123: Allow per stream/table timestamp extractor

Thanks, Jeyhun! I observed that there is still on ongoing conversation in the DISCUSS thread, so perhaps this voting thread was started a bit too early? -Michael On Tue, Feb 28, 2017 at 10:35 AM, Damian Guy wrote: > Thanks for the KIP Jeyhun! > > +1 > > On Tue, 28 Feb

[jira] [Commented] (KAFKA-4779) Failure in kafka/tests/kafkatest/tests/core/security_rolling_upgrade_test.py

[ https://issues.apache.org/jira/browse/KAFKA-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15887934#comment-15887934 ] Ismael Juma commented on KAFKA-4779: Thanks [~rsivaram]! Hopefully this is the last issue uncovered by

[jira] [Commented] (KAFKA-4779) Failure in kafka/tests/kafkatest/tests/core/security_rolling_upgrade_test.py

[ https://issues.apache.org/jira/browse/KAFKA-4779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15887913#comment-15887913 ] Rajini Sivaram commented on KAFKA-4779: --- The new failure looks like a very different issue. The

Re: [VOTE] KIP-119: Drop Support for Scala 2.10 in Kafka 0.11

+1 (non-binding) On Tue, 28 Feb 2017 at 11:42, Molnár Bálint wrote: > +1 > > 2017-02-28 12:17 GMT+01:00 Dongjin Lee : > > > > > > > +1. > > > > > > > > Best, > > > > Dongjin > > > > > > -- > > > > > > > > > > Dongjin Lee > > > > > > > > > > > >

Re: [DISCUSS] 0.10.3.0/0.11.0.0 release planning

Ismael, Thank you for volunteering to manage the next release. +1 for 0.11.0.0 Regards, Rajini On Tue, Feb 28, 2017 at 11:02 AM, Ismael Juma wrote: > Hi Ofir, > > Thanks for the feedback. This will be the first release with exactly-once. > I think we should give ourselves

Re: [DISCUSS] KIP-82 - Add Record Headers

Hi Becket, Comments inline. On Sat, Feb 25, 2017 at 10:33 PM, Becket Qin wrote: > > 1. Regarding the mutability. > > I think it would be a big convenience to have headers mutable during > certain stage in the message life cycle for the use cases you mentioned. I > agree

[GitHub] kafka pull request #2607: MINOR: Fix typo in javadoc of `flatMapValues`

GitHub user miguno opened a pull request: https://github.com/apache/kafka/pull/2607 MINOR: Fix typo in javadoc of `flatMapValues` You can merge this pull request into a Git repository by running: $ git pull https://github.com/miguno/kafka trunk-flatMapValues-docstring

Re: [VOTE] KIP-119: Drop Support for Scala 2.10 in Kafka 0.11

+1 2017-02-28 12:17 GMT+01:00 Dongjin Lee : > > > +1. > > > > Best, > > Dongjin > > > -- > > > > > Dongjin Lee > > > > > > Software developer in Line+. > > So interested in massive-scale machine learning. > > > > facebook: www.facebook.com/dongjin.lee.kr

Re: [VOTE] KIP-119: Drop Support for Scala 2.10 in Kafka 0.11

+1. Best, Dongjin -- Dongjin Lee Software developer in Line+. So interested in massive-scale machine learning. facebook: www.facebook.com/dongjin.lee.kr (http://www.facebook.com/dongjin.lee.kr) linkedin: kr.linkedin.com/in/dongjinleekr

Re: [DISCUSS] 0.10.3.0/0.11.0.0 release planning

Hi Jeff, I share your desire to streamline the experience and remove options that don't make sense to new users. I should, however, point out that we won't be able to remove the old consumers in 0.11.0.0 as they haven't been deprecated yet. Hopefully that will happen in 0.12.0.0/1.0.0. Ismael

Re: [DISCUSS] 0.10.3.0/0.11.0.0 release planning

Hi Ofir, Thanks for the feedback. This will be the first release with exactly-once. I think we should give ourselves at least one stabilisation/polish/feedback cycle before we go for 1.0. :) Ismael On Tue, Feb 28, 2017 at 10:55 AM, Ofir Manor wrote: > This is definitely

Re: [DISCUSS] 0.10.3.0/0.11.0.0 release planning

This is definitely a major release, looks already quite exciting... I don't want to start a bike-shading argument, but a few people have told me in the past year that once exactly-once delivery lands, Kafka would likely bump to 1.0. I do like it, but don't feel strongly either way. Ofir Manor

[jira] [Commented] (KAFKA-4812) We are facing the same issue as SAMZA-590 for kafka

[ https://issues.apache.org/jira/browse/KAFKA-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15887779#comment-15887779 ] Manjeer Srujan. Y commented on KAFKA-4812: -- [~criccomini]: Seems like you have fixed it in Samza

[VOTE] KIP-119: Drop Support for Scala 2.10 in Kafka 0.11

Hi everyone, Since the few who responded in the discuss thread were in favour and there were no objections, I would like to initiate the voting process for KIP-119: Drop Support for Scala 2.10 in Kafka 0.11:

[jira] [Updated] (KAFKA-4812) We are facing the same issue as SAMZA-590 for kafka

[ https://issues.apache.org/jira/browse/KAFKA-4812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manjeer Srujan. Y updated KAFKA-4812: - Summary: We are facing the same issue as SAMZA-590 for kafka (was: We are facing the

Re: [DISCUSS] KIP-123: Allow per stream/table timestamp extractor

Hi Jeyhun, I mean something slightly different. In your motivation you say "joining multiple streams/tables that require different timestamp extraction methods". I wan to understand the scope of this. Is it allowed to have a stream that uses wallclock time join a stream that uses event time?

[jira] [Created] (KAFKA-4812) We are facing the same issue as SAMZA-590

Manjeer Srujan. Y created KAFKA-4812: Summary: We are facing the same issue as SAMZA-590 Key: KAFKA-4812 URL: https://issues.apache.org/jira/browse/KAFKA-4812 Project: Kafka Issue Type:

Re: [DISCUSS] 0.10.3.0/0.11.0.0 release planning

Hi Vahid, Sure, I've added KIP-54. I thought I had done it, sorry for the oversight. Ismael On Tue, Feb 28, 2017 at 4:31 AM, Vahid S Hashemian < vahidhashem...@us.ibm.com> wrote: > +1 on 0.11.0.0. > > Can we also include KIP-54 to the list? > The PR for this KIP is ready for review. > >

Re: [DISCUSS] KIP-123: Allow per stream/table timestamp extractor

Hi Eno, Thanks for feedback. I think you mean [1]. In this KIP we do not consider the situations you mentioned. So, either we can extend the KIP and solve mentioned issues or submit 2 PRs incrementally. [1] https://issues.apache.org/jira/browse/KAFKA-4785 Cheers, Jeyhun On Tue, Feb 28, 2017

Re: [DISCUSS] KIP-112: Handle disk failure for JBOD

Makes sense, thank you Dong. Eno > On 28 Feb 2017, at 01:51, Dong Lin wrote: > > Hi Jun, > > In addition to the Eno's reference of why rebuild time with RAID-5 is more > expensive, another concern is that RAID-5 will fail if more than one disk > fails. JBOD is still works

Re: [DISCUSS] KIP-123: Allow per stream/table timestamp extractor

Hi Jeyhun, Thanks for the KIP, sorry I'm coming a bit late to the discussion. One thing I'd like to understand is whether we can avoid situations where the user is mixing different times (event time vs. wallclock time) in their processing inadvertently. Before this KIP, all the relevant topics

Re: [DISCUSS] 0.10.3.0/0.11.0.0 release planning

+1 On Tue, 28 Feb 2017 at 04:32 Vahid S Hashemian wrote: > +1 on 0.11.0.0. > > Can we also include KIP-54 to the list? > The PR for this KIP is ready for review. > > Thanks. > --Vahid > > > > > > From: Ismael Juma > To: dev@kafka.apache.org >

Re: [VOTE] KIP-123: Allow per stream/table timestamp extractor

Thanks for the KIP Jeyhun! +1 On Tue, 28 Feb 2017 at 08:59 Jeyhun Karimov wrote: > Dear community, > > I'd like to start the vote for KIP-123: > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=68714788 > > > Cheers, > Jeyhun > -- > -Cheers > > Jeyhun >

[VOTE] KIP-123: Allow per stream/table timestamp extractor

Dear community, I'd like to start the vote for KIP-123: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=68714788 Cheers, Jeyhun -- -Cheers Jeyhun

<    1   2