[jira] [Resolved] (KAFKA-8344) Fix vagrant-up.sh to work with AWS properly

[ https://issues.apache.org/jira/browse/KAFKA-8344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira resolved KAFKA-8344. - Resolution: Fixed Fix Version/s: 2.3.0 > Fix vagrant-up.sh to work with AWS properly >

Build failed in Jenkins: kafka-trunk-jdk11 #506

See Changes: [cshapi] MINOR: docs typo in '--zookeeper myhost:2181--execute' -- Started by an SCM change [EnvInject] - Loading node environment variables. Building

Build failed in Jenkins: kafka-2.1-jdk8 #185

See Changes: [rhauch] MINOR: Remove header and key/value converter config value logging -- [...truncated 2.58 MB...] org.apache.kafka.streams.StreamsBuilderTest >

Build failed in Jenkins: kafka-2.0-jdk8 #261

See Changes: [rhauch] MINOR: Remove header and key/value converter config value logging -- [...truncated 434.64 KB...] kafka.controller.ReplicaStateMachineTest >

Jenkins build is back to normal : kafka-1.1-jdk7 #262

See

Build failed in Jenkins: kafka-2.0-jdk8 #260

See Changes: [jason] KAFKA-6789; Handle retriable group errors in AdminClient API (#5578) -- [...truncated 2.51 MB...] org.apache.kafka.streams.TopologyTest >

Build failed in Jenkins: kafka-trunk-jdk11 #505

See Changes: [rhauch] KAFKA-8231: Expansion of ConnectClusterState interface (#6584) [rhauch] MINOR: Remove header and key/value converter config value logging --

Build failed in Jenkins: kafka-trunk-jdk8 #3615

See Changes: [jason] KAFKA-6789; Handle retriable group errors in AdminClient API (#5578) [bbejeck] KAFKA-8324: Add close() method to RocksDBConfigSetter (#6697) --

[jira] [Resolved] (KAFKA-8231) Expansion of ConnectClusterState interface

[ https://issues.apache.org/jira/browse/KAFKA-8231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-8231. -- Resolution: Fixed > Expansion of ConnectClusterState interface >

Re: [VOTE] KIP-458: Connector Client Config Override Policy

I'm still +1 and like the simplification. Randall On Thu, May 9, 2019 at 5:54 PM Magesh Nandakumar wrote: > I have updated the KIP to remove the `Ignore` policy and also the > useOverrides() > method in the interface. > Thanks a lot for your thoughts, Colin. I believe this certainly simplifies

Build failed in Jenkins: kafka-2.1-jdk8 #184

See Changes: [jason] KAFKA-6789; Handle retriable group errors in AdminClient API (#5578) -- [...truncated 467.53 KB...] kafka.zk.ReassignPartitionsZNodeTest >

[jira] [Resolved] (KAFKA-8313) KafkaStreams state not being updated properly after shutdown

[ https://issues.apache.org/jira/browse/KAFKA-8313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-8313. -- Resolution: Fixed Assignee: Guozhang Wang Fix Version/s: 2.3.0 > KafkaStreams

[jira] [Created] (KAFKA-8347) Choose next record to process by timestamp

Sophie Blee-Goldman created KAFKA-8347: -- Summary: Choose next record to process by timestamp Key: KAFKA-8347 URL: https://issues.apache.org/jira/browse/KAFKA-8347 Project: Kafka Issue

[jira] [Created] (KAFKA-8346) Improve replica fetcher behavior in handling partition failures

Aishwarya Gune created KAFKA-8346: - Summary: Improve replica fetcher behavior in handling partition failures Key: KAFKA-8346 URL: https://issues.apache.org/jira/browse/KAFKA-8346 Project: Kafka

Re: Hello, I`d like to get access right to contribute kafka.

Hello WooYoung, I saw your name on contributors list already, you should be good to go now. Thanks for your interest in contributing to Kafka! Guozhang On Thu, May 9, 2019 at 8:08 AM WooYoung Jeong wrote: > These days I`m analyzing Kafka source project. > I`m interested in contributing

Build failed in Jenkins: kafka-trunk-jdk11 #504

See Changes: [jason] KAFKA-6789; Handle retriable group errors in AdminClient API (#5578) [bbejeck] KAFKA-8324: Add close() method to RocksDBConfigSetter (#6697) --

[jira] [Resolved] (KAFKA-6789) Add retry logic in AdminClient requests

[ https://issues.apache.org/jira/browse/KAFKA-6789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6789. Resolution: Fixed Fix Version/s: 2.2.2 2.1.2

Re: [DISCUSS] KIP-429 : Smooth Auto-Scaling for Kafka Streams

Hello Matthias, I'm proposing to change this behavior holistically inside ConsumerCoordinator actually. In other words I'm trying to piggy-back this behavioral fix of KAFKA-4600 along with this KIP, and the motivation for me to do this piggy-backing is that, with incremental rebalancing, there

Re: [VOTE] KIP-458: Connector Client Config Override Policy

I have updated the KIP to remove the `Ignore` policy and also the useOverrides() method in the interface. Thanks a lot for your thoughts, Colin. I believe this certainly simplifies the KIP. On Thu, May 9, 2019 at 3:44 PM Magesh Nandakumar wrote: > Unless anyone has objections, I'm going to

Re: [VOTE] KIP-458: Connector Client Config Override Policy

Unless anyone has objections, I'm going to update the KIP to remove the `Ignore` policy and make `None` as the default. I will also remove the ` default boolean useOverrides()` in the interface which was introduced for the purpose of backward compatibility. On Thu, May 9, 2019 at 3:27 PM Randall

Re: golang library for kafka streams

cc'ing Magnus who may have some ideas :) Guozhang On Thu, May 9, 2019 at 9:48 AM Jay Heydt wrote: > any estimate of when a kafka streams library will be available for golang? > -- -- Guozhang

Re: [VOTE] KIP-464: Defaults for AdminClient#createTopic

Thanks Colin! Since the discussion around the builder is here I'll copy over my comment from the discuss thread: If we want the flexibility that the builder provides we would need to add three constructors: - no partitions/replicas - just partitions - just replicas I see good use cases for the

Re: [VOTE] KIP-458: Connector Client Config Override Policy

I have also seen users include in connector configs the `producer.*` and `consumer.*` properties that should go into the worker configs. But those don't match, and the likelihood that someone is already using `producer.override.*` or `consumer.override.*` properties in their connector configs does

Re: [VOTE] KIP-458: Connector Client Config Override Policy

To add more details regarding the backward compatibility; I have generally seen users trying to set "producer.request.timeout.ms " in their connector config under the assumption that it will get used and would never come back to remove it. The initial

Re: [VOTE] KIP-458: Connector Client Config Override Policy

Colin, Thanks a lot for the feedback. As you said, the possibilities of someone having "producer.override.request.timeout.ms" in their connector config in AK 2.2 or lower is very slim. But the key thing is if in case, someone has it AK2.2 doesn't do anything with it and it silently ignores the

Re: [VOTE] KIP-465: Add Consolidated Connector Endpoint to Connect REST API

After 80 hours, the results of the voting: +3 binding +1 non-binding (+1 from me too :) I'll update this wiki to show this KIP as approved. 拾 thanks dan On Thu, May 9, 2019 at 8:11 AM Rajini Sivaram wrote: > Hi Dan, > > Thanks for the KIP, +1 (binding) > > Regards, > > Rajini > > > On Mon,

Re: [VOTE] KIP-464: Defaults for AdminClient#createTopic

+1 (binding). Re: the builder discussion. I don't feel strongly either way-- the builder sketched out in the KIP looks reasonable, but I can also understand Ismael's argument for keeping the KIP minimal. best, Colin On Thu, May 9, 2019, at 08:09, Randall Hauch wrote: > I'm fine with

Build failed in Jenkins: kafka-trunk-jdk8 #3614

See Changes: [cmccabe] KAFKA-8332: Refactor ImplicitLinkedHashSet to avoid losing ordering when -- [...truncated 2.41 MB...]

Build failed in Jenkins: kafka-2.1-jdk8 #183

See Changes: [matthias] KAFKA-8240: Fix NPE in Source.equals() (#6685) -- [...truncated 459.43 KB...] kafka.server.AbstractFetcherThreadTest >

Re: [VOT] KIP-449: Add connector contexts to Connect worker logs (vote thread)

Thanks everyone! The vote has been open for about 9 days, and the KIP is adopted with +4 binding votes (Randall, Manikumar, Gwen, and Bill) and no -1 votes. Thanks also to Jeremy, Magesh, Chris, and Konstantine for their non-binding votes. On Thu, May 9, 2019 at 1:59 PM Bill Bejeck wrote: > +1

Re: [VOT] KIP-449: Add connector contexts to Connect worker logs (vote thread)

+1 (binding) Makes a lot of sense to me. -Bill On Thu, May 9, 2019 at 2:05 PM Gwen Shapira wrote: > +1 (binding) > Hell yeah! > > On Mon, Apr 29, 2019 at 3:34 PM Randall Hauch wrote: > > > I would like to start the vote for KIP-258: > > > > > > >

Re: [VOTE] KIP-453: Add close() method to RocksDBConfigSetter

Thanks everyone for voting! Closing the vote on this KIP which passes with three +1 (binding) from Guozhang, Bill, and Matthias, and two +1 (non-binding) from Kamal and John. For those interested you can check out the PR here: https://github.com/apache/kafka/pull/6697 On Tue, May 7, 2019 at 7:31

Build failed in Jenkins: kafka-trunk-jdk11 #503

See Changes: [cmccabe] KAFKA-8332: Refactor ImplicitLinkedHashSet to avoid losing ordering when -- Started by an SCM change [EnvInject] - Loading node environment

Re: [DISCUSS] KIP-466: Add support for List serialization and deserialization

Hey Sophie, Thank you for your input. I think I’d rather finish this KIP as is, and then open a new one for the Collections (if everyone agrees). I don’t want to extend the current KIP-466, since most of the work is already done for it. Meanwhile, I’ll start adding some test cases for this new

Re: [VOT] KIP-449: Add connector contexts to Connect worker logs (vote thread)

+1 (binding) Hell yeah! On Mon, Apr 29, 2019 at 3:34 PM Randall Hauch wrote: > I would like to start the vote for KIP-258: > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-449%3A+Add+connector+contexts+to+Connect+worker+logs > > The KIP uses the Mapped Diagnostic Contexts (MDC)

Re: [VOTE] KIP-461 Improve Replica Fetcher behavior at handling partition failure

Thanks for the KIP. +1(binding) Thanks, Harsha On May 9, 2019, 9:58 AM -0700, Jun Rao , wrote: > Hi, Aishwarya, > > Thanks for the KIP. +1 > > Jun > > On Wed, May 8, 2019 at 4:30 PM Aishwarya Gune > wrote: > > > Hi All! > > > > I would like to call for a vote on KIP-461 that would improve the

Re: [DISCUSS] KIP-466: Add support for List serialization and deserialization

Good point about serdes for other Collections. On the one hand I'd guess that non-List Collections are probably relatively rare in practice (if anyone disagrees please correct me!) but on the other hand, a) even if just a small number of people benefit I think it's worth the extra effort and b) if

Re: [VOTE] KIP-461 Improve Replica Fetcher behavior at handling partition failure

Hi, Aishwarya, Thanks for the KIP. +1 Jun On Wed, May 8, 2019 at 4:30 PM Aishwarya Gune wrote: > Hi All! > > I would like to call for a vote on KIP-461 that would improve the behavior > of replica fetcher in case of partition failure. The fetcher thread would > just stop monitoring the

Re: [DISCUSS] KIP-464 Default Replication Factor for AdminClient#createTopic

Moving discussion on VOTE thread here: Ismael asked: > Adding a Builder seems unrelated to this change. Do we need it? Given the > imminent KIP deadline, I'd keep it simple and just have the constructor > with just the name parameter. If we want the flexibility that the builder provides we

golang library for kafka streams

any estimate of when a kafka streams library will be available for golang?

Re: [VOTE] KIP-455: Create an Administrative API for Replica Reassignment

+1 (non-binding) Thanks for the KIP, Colin! On Thu, May 9, 2019 at 8:27 AM Colin McCabe wrote: > Hi Viktor, > > There is a jira -- KAFKA-8345. The PR is not quite ready yet, but > hopefully soon :) > > best, > Colin > > On Thu, May 9, 2019, at 01:13, Viktor Somogyi-Vass wrote: > > +1

Build failed in Jenkins: kafka-trunk-jdk8 #3613

See Changes: [github] MINOR: Fix bug in Struct.equals and use Objects.equals/Long.hashCode [github] MINOR: improve JavaDocs for KStream.through() (#6639) --

Re: [DISCUSS] KIP-382: MirrorMaker 2.0

Hey y'all, I'm happy to announce that the PR for "MirrorMaker 2.0" is ready for review, after a long spell in "draft". https://github.com/apache/kafka/pull/6295 MirrorMaker 2.0 is in the Kafka 2.3.0 release plan. Please take a look so we can get this merged. Also, shameless plug: I'm giving a

Re: [VOTE] KIP-455: Create an Administrative API for Replica Reassignment

Hi Viktor, There is a jira -- KAFKA-8345. The PR is not quite ready yet, but hopefully soon :) best, Colin On Thu, May 9, 2019, at 01:13, Viktor Somogyi-Vass wrote: > +1 (non-binding) > > Thanks Colin, this is great stuff. Does a jira (or maybe even a PR :) ) for > this exist yet? > >

Re: [VOT] KIP-449: Add connector contexts to Connect worker logs (vote thread)

HI Randall, +1 (binding), Thanks for the KIP. Thanks, Manikumar On Wed, May 8, 2019 at 4:29 AM Randall Hauch wrote: > +1 (binding) > > On Mon, May 6, 2019 at 3:53 PM Konstantine Karantasis < > konstant...@confluent.io> wrote: > > > Great improvement for multi-tenancy. > > Thanks Randall! > >

[jira] [Created] (KAFKA-8345) Create an Administrative API for Replica Reassignment

Colin P. McCabe created KAFKA-8345: -- Summary: Create an Administrative API for Replica Reassignment Key: KAFKA-8345 URL: https://issues.apache.org/jira/browse/KAFKA-8345 Project: Kafka

Re: [VOTE] KIP-440: Extend Connect Converter to support headers

+1 (non-binding). Looks good. On 09/05/2019, 15:55, "Gwen Shapira" wrote: +1 (binding) Thank you! On Mon, May 6, 2019, 11:25 PM Yaroslav Tkachenko wrote: > Hi everyone, > > I'd like to start a vote for KIP-440: Extend Connect Converter to support >

Re: [VOTE] KIP-465: Add Consolidated Connector Endpoint to Connect REST API

Hi Dan, Thanks for the KIP, +1 (binding) Regards, Rajini On Mon, May 6, 2019 at 8:08 PM Konstantine Karantasis < konstant...@confluent.io> wrote: > Useful and concise KIP > > +1 (non-binding) > > Konstantine > > On Mon, May 6, 2019 at 10:43 AM Randall Hauch wrote: > > > Thanks, Dan. As

Re: [VOTE] KIP-465: Add Consolidated Connector Endpoint to Connect REST API

Great improvement, I definitely missed having a simple API for status. +1 (binding) On Mon, May 6, 2019, 7:23 AM dan wrote: > I would like to start voting for > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-465%3A+Add+Consolidated+Connector+Endpoint+to+Connect+REST+API > > thanks >

Re: [VOTE] KIP-464: Defaults for AdminClient#createTopic

I'm fine with simplifying the KIP by removing the Builder (which seems ancillary), or keeping the KIP as-is. I'll wait to vote until Almog says which way he'd like to proceed. On Thu, May 9, 2019 at 9:45 AM Ismael Juma wrote: > Hi Almog, > > Adding a Builder seems unrelated to this change. Do

Hello, I`d like to get access right to contribute kafka.

These days I`m analyzing Kafka source project. I`m interested in contributing Kafka Project, so I have commented that to assign me on a Jira ticket. It is https://issues.apache.org/jira/browse/KAFKA-8311 However, I have no right to access Jira and wiki. So Could you give me access ? Thank you,

Re: [VOTE] KIP-458: Connector Client Config Override Policy

Hi Magesh, Thanks for the KIP, +1 (binding) Regards, Rajini On Thu, May 9, 2019 at 3:55 PM Randall Hauch wrote: > Nice work, Magesh. > > +1 (binding) > > Randall > > On Wed, May 8, 2019 at 7:22 PM Magesh Nandakumar > wrote: > > > Thanks a lot Chris. So far, the KIP has one non-binding vote

Re: [VOTE] KIP-437: Custom replacement for MaskField SMT

Nice work, Valeria. +1 (binding) Randall On Mon, May 6, 2019 at 4:30 PM Konstantine Karantasis < konstant...@confluent.io> wrote: > I think is is a useful improvement proposal. Thanks Valeria! > > I'm +1 (non-binding) on this KIP > > Konstantine > > On Mon, Apr 15, 2019 at 2:04 AM Valeria

Re: [VOTE] KIP-458: Connector Client Config Override Policy

Nice work, Magesh. +1 (binding) Randall On Wed, May 8, 2019 at 7:22 PM Magesh Nandakumar wrote: > Thanks a lot Chris. So far, the KIP has one non-binding vote and I'm still > looking forward to the KIP to be voted by Friday's deadline. > > On Tue, May 7, 2019 at 10:00 AM Chris Egerton wrote:

Re: [VOTE] KIP-440: Extend Connect Converter to support headers

+1 (binding) Thank you! On Mon, May 6, 2019, 11:25 PM Yaroslav Tkachenko wrote: > Hi everyone, > > I'd like to start a vote for KIP-440: Extend Connect Converter to support > headers ( > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-440%3A+Extend+Connect+Converter+to+support+headers >

Re: [VOTE] KIP-464: Defaults for AdminClient#createTopic

Hi Almog, Adding a Builder seems unrelated to this change. Do we need it? Given the imminent KIP deadline, I'd keep it simple and just have the constructor with just the name parameter. Ismael On Thu, May 2, 2019 at 1:58 AM Mickael Maison wrote: > I was planning to write a KIP for the exact

Build failed in Jenkins: kafka-trunk-jdk11 #502

See Changes: [github] MINOR: improve JavaDocs for KStream.through() (#6639) -- Started by an SCM change [EnvInject] - Loading node environment variables. Building

Re: [DISCUSS] KIP-466: Add support for List serialization and deserialization

Hey, I don’t see any replies. Seems like this proposal can be finalized and called for a vote? Also I’ve been thinking. Do we need more serdes for other Collections? Like queue or set for example Best, Daniyar Yeralin > On May 8, 2019, at 2:28 PM, John Roesler wrote: > > Hi Daniyar, > >

Re: [VOTE] KIP-440: Extend Connect Converter to support headers

Thanks, Yaroslav! +1 (binding) Randall On Tue, May 7, 2019 at 1:25 AM Yaroslav Tkachenko wrote: > Hi everyone, > > I'd like to start a vote for KIP-440: Extend Connect Converter to support > headers ( > >

[jira] [Resolved] (KAFKA-8240) Source.equals() can fail with NPE

[ https://issues.apache.org/jira/browse/KAFKA-8240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-8240. Resolution: Fixed Fix Version/s: 2.2.2 2.1.2

Build failed in Jenkins: kafka-trunk-jdk11 #501

See Changes: [github] MINOR: Fix bug in Struct.equals and use Objects.equals/Long.hashCode -- Started by an SCM change [EnvInject] - Loading node environment variables.

Re: [DISCUSS] KIP-429 : Smooth Auto-Scaling for Kafka Streams

Thanks Guozhang! The simplified upgrade path is great! Just a clarification question about the "Rebalance Callback Error Handling" -- does this change affect the `ConsumerCoordinator` only if incremental rebalancing is use? Or does the behavior also change for the eager rebalancing case?

Re: [DISCUSS] KIP-456: Helper classes to make it simpler to write test logic with TopologyTestDriver

Hi Jukka Sorry, that was mostly what I had in mind, I didn't have enough time to look through the KIP. My question was also if this handling of topics wouldn't make more sense even outside the TTD, for the general API. regards Patrik On Thu, 9 May 2019 at 14:43, Jukka Karvanen wrote: > Hi

Re: [DISCUSS] KIP-456: Helper classes to make it simpler to write test logic with TopologyTestDriver

Hi Patrick, Sorry, I need to clarify. In this current version of KIP in wiki, topic object are created with constructor where driver, topicName and serdes are provided. TestInputTopic inputTopic = new TestInputTopic(testDriver, INPUT_TOPIC, new Serdes.StringSerde(), new Serdes.StringSerde());

Re: [DISCUSS] KIP-456: Helper classes to make it simpler to write test logic with TopologyTestDriver

Hi Jukka Regarding your comment > If there would be a way to find out needed serders for the topic, it would make API even simpler. I was wondering if it wouldn't make more sense to have a "topic object" including the Serdes and use this instead of only passing in the name as a string everywhere.

Re: [DISCUSS] KIP-456: Helper classes to make it simpler to write test logic with TopologyTestDriver

Hi, I will write new KIP for the TestTopologyDriver Input and Output usability changes. It is out of the scope of the current title: "Helper classes to make it simpler to write test logic with TopologyTestDriver" and we can get back to this KIP if that alternative is not favored. So my original

Re: [VOTE] KIP-455: Create an Administrative API for Replica Reassignment

+1 (non-binding) Thanks Colin, this is great stuff. Does a jira (or maybe even a PR :) ) for this exist yet? Viktor On Thu, May 9, 2019 at 7:23 AM Colin McCabe wrote: > Hi all, > > I'd like to start the vote for KIP-455: Create an Administrative API for > Replica Reassignment. I think this

[jira] [Created] (KAFKA-8344) Fix vagrant-up.sh to work with AWS properly

Kengo Seki created KAFKA-8344: - Summary: Fix vagrant-up.sh to work with AWS properly Key: KAFKA-8344 URL: https://issues.apache.org/jira/browse/KAFKA-8344 Project: Kafka Issue Type: Bug

Re: [VOTE] KIP-461 Improve Replica Fetcher behavior at handling partition failure

+1 (binding) Thank you! I especially like the new metric for tracking the partitions with errors. Its those little things :) On Wed, May 8, 2019 at 4:30 PM Aishwarya Gune wrote: > Hi All! > > I would like to call for a vote on KIP-461 that would improve the behavior > of replica fetcher in