[jira] [Created] (KAFKA-7802) Connection to Broker Disconnected Taking Down the Whole Cluster

Candice Wan created KAFKA-7802: -- Summary: Connection to Broker Disconnected Taking Down the Whole Cluster Key: KAFKA-7802 URL: https://issues.apache.org/jira/browse/KAFKA-7802 Project: Kafka

[jira] [Created] (KAFKA-7801) TopicCommand should not be able to alter transaction topic partition count

huxihx created KAFKA-7801: - Summary: TopicCommand should not be able to alter transaction topic partition count Key: KAFKA-7801 URL: https://issues.apache.org/jira/browse/KAFKA-7801 Project: Kafka

Jenkins build is back to normal : kafka-trunk-jdk11 #192

See

Re: [DISCUSS] Kafka 2.2.0 in February 2018

Thanks for volunteering Matthias! The plan sounds good to me. Ismael On Tue, Jan 8, 2019, 1:07 PM Matthias J. Sax Hi all, > > I would like to propose a release plan (with me being release manager) > for the next time-based feature release 2.2.0 in February. > > The recent Kafka release history

Re: [DISCUSS] KIP-411: Add option to make Kafka Connect task client ID values unique

Hi, Paul. I concur with the others, and I like the new approach that avoids a new configuration, especially because it does not change the behavior for anyone already using `producer.client.id` and/or `consumer.client.id`. I did leave a few comments on the PR. Perhaps the biggest one is whether

[VOTE] KIP-414: Expose Embedded ClientIds in Kafka Streams

Hello folks, I'd like to start a voting process for the following KIP: https://cwiki.apache.org/confluence/display/KAFKA/KIP-414%3A+Expose+Embedded+ClientIds+in+Kafka+Streams It is a pretty straight-forward and small augment to Stream's public ThreadMetadata interface, as an outcome of the

Jenkins build is back to normal : kafka-trunk-jdk8 #3293

See

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

See Changes: [github] MINOR: code cleanup (#6056) [wangguoz] MINOR: Put states in proper order, increase timeout for starting (#6105) -- [...truncated 2.25 MB...]

Re: [DISCUSSION] KIP-412: Extend Admin API to support dynamic application log levels

> To differentiate between the normal Kafka config settings and the application's log level settings, we will introduce a new resource type - BROKER_LOGGERS Stanislav, can you explain why log level wouldn't be a "normal Kafka config setting"? Ryanne On Tue, Jan 8, 2019, 4:26 PM Stanislav

[DISCUSS] KIP-300: Add Windowed KTable API in StreamsBuilder

Hey folks, I would like to start a discussion thread on adding new time/session windowed KTable APIs for KStream: https://cwiki.apache.org/confluence/display/KAFKA/KIP-300%3A+Add+Windowed+KTable+API+in+StreamsBuilder We have been working on this thread around 7 months ago, and it is

[jira] [Created] (KAFKA-7800) Extend Admin API to support dynamic application log levels

Stanislav Kozlovski created KAFKA-7800: -- Summary: Extend Admin API to support dynamic application log levels Key: KAFKA-7800 URL: https://issues.apache.org/jira/browse/KAFKA-7800 Project: Kafka

[DISCUSSION] KIP-412: Extend Admin API to support dynamic application log levels

Hey there everybody, I'd like to start a discussion about KIP-412. Please take a look at the KIP if you can, I would appreciate any feedback :) KIP: KIP-412 JIRA: KAFKA-7800

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

See Changes: [manikumar.reddy] MINOR: Update command line options in Authorization and ACLs [jason] KAFKA-7253; The returned connector type is always null when creating --

[jira] [Created] (KAFKA-7799) Fix flaky test RestServerTest.testCORSEnabled

Jason Gustafson created KAFKA-7799: -- Summary: Fix flaky test RestServerTest.testCORSEnabled Key: KAFKA-7799 URL: https://issues.apache.org/jira/browse/KAFKA-7799 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-7798) Expose embedded client context from KafkaStreams threadMetadata

Guozhang Wang created KAFKA-7798: Summary: Expose embedded client context from KafkaStreams threadMetadata Key: KAFKA-7798 URL: https://issues.apache.org/jira/browse/KAFKA-7798 Project: Kafka

[jira] [Created] (KAFKA-7797) Replication throttling configs aren't in the docs

James Cheng created KAFKA-7797: -- Summary: Replication throttling configs aren't in the docs Key: KAFKA-7797 URL: https://issues.apache.org/jira/browse/KAFKA-7797 Project: Kafka Issue Type:

Re: [VOTE] KIP-345: Introduce static membership protocol to reduce consumer rebalances

Hey friends, we will be closing this vote thread since we already got 3 binding votes (Guozhang, Harsha and Jason), and 2 non-binding votes (Stanislav, Mayuresh). Thanks again for everyone who have been actively contributing to this thread (Dong, Matthias, Colin, Mike, John, Konstantine), this

[DISCUSS] Kafka 2.2.0 in February 2018

Hi all, I would like to propose a release plan (with me being release manager) for the next time-based feature release 2.2.0 in February. The recent Kafka release history can be found at https://cwiki.apache.org/confluence/display/KAFKA/Future+release+plan. The release plan (with open issues and

[jira] [Resolved] (KAFKA-7051) Improve the efficiency of the ReplicaManager when there are many partitions

[ https://issues.apache.org/jira/browse/KAFKA-7051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-7051. Resolution: Fixed > Improve the efficiency of the ReplicaManager when there are many

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

See Changes: [rajinisivaram] KAFKA-7773; Add end to end system test relying on verifiable consumer -- [...truncated 4.51 MB...]

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

See Changes: [jason] KAFKA-7253; The returned connector type is always null when creating -- [...truncated 2.26 MB...]

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

See Changes: [jason] KAFKA-7253; The returned connector type is always null when creating -- [...truncated 437.65 KB...] kafka.coordinator.group.GroupMetadataTest >

[jira] [Created] (KAFKA-7796) structured streaming fetched wrong current offset from kafka

Ryne Yang created KAFKA-7796: Summary: structured streaming fetched wrong current offset from kafka Key: KAFKA-7796 URL: https://issues.apache.org/jira/browse/KAFKA-7796 Project: Kafka Issue

[jira] [Created] (KAFKA-7795) Broker fails on duplicate configuration keys

David Arthur created KAFKA-7795: --- Summary: Broker fails on duplicate configuration keys Key: KAFKA-7795 URL: https://issues.apache.org/jira/browse/KAFKA-7795 Project: Kafka Issue Type:

Re: [VOTE] KIP-396: Add Commit/List Offsets Operations to AdminClient

+1 (non-binding) Thanks Mickael! On Tue, 8 Jan 2019 at 17:39, Patrik Kleindl wrote: > +1 (non-binding) > Thanks, sounds very helpful > Best regards > Patrik > > > Am 08.01.2019 um 18:10 schrieb Mickael Maison >: > > > > Hi all, > > > > I'd like to start the vote on KIP-396: > > >

Re: [VOTE] KIP-396: Add Commit/List Offsets Operations to AdminClient

+1 (non-binding) Thanks, sounds very helpful Best regards Patrik > Am 08.01.2019 um 18:10 schrieb Mickael Maison : > > Hi all, > > I'd like to start the vote on KIP-396: > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=97551484 > > Thanks

[jira] [Created] (KAFKA-7794) kafka.tools.GetOffsetShell does not return the offset in some cases

Daniele Ascione created KAFKA-7794: -- Summary: kafka.tools.GetOffsetShell does not return the offset in some cases Key: KAFKA-7794 URL: https://issues.apache.org/jira/browse/KAFKA-7794 Project: Kafka

[VOTE] KIP-391: Allow Producing with Offsets for Cluster Replication

Hi All, I'd like to start a vote on KIP-391 https://cwiki.apache.org/confluence/display/KAFKA/KIP-391%3A+Allow+Producing+with+Offsets+for+Cluster+Replication thanks! PS - Discussion thread https://lists.apache.org/list.html?dev@kafka.apache.org:lte=3M:KIP-391

Re: [DISCUSS] KIP-409: Allow creating under-replicated topics and partitions

Hi, We've not received any feedback yet on this KIP. We still believe this would be a nice improvement. Thanks On Tue, Dec 18, 2018 at 4:27 PM Mickael Maison wrote: > > Hi, > > We have submitted a KIP to handle topics and partitions creation when > a cluster is not fully available: > >

[VOTE] KIP-396: Add Commit/List Offsets Operations to AdminClient

Hi all, I'd like to start the vote on KIP-396: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=97551484 Thanks

[jira] [Resolved] (KAFKA-7253) The connector type responded by worker is always null when creating connector

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

Jenkins build is back to normal : kafka-trunk-jdk11 #189

See

[jira] [Reopened] (KAFKA-5117) Kafka Connect REST endpoints reveal Password typed values

[ https://issues.apache.org/jira/browse/KAFKA-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch reopened KAFKA-5117: -- Assignee: Randall Hauch (was: Ewen Cheslack-Postava) I'm reopening this because there

Implementing a custom request

Dear all, I'm planning to implement a custom network request where a Consumer requests some partition metadata from a broker(s). I would like to know if there are some references on what to consider when implementing a new request. Since there are already quite a range of different network

Re: [DISCUSS] KIP-252: Extend ACLs to allow filtering based on ip ranges and subnets

Hi Colin, thanks for your response! in theory we could get away without any additional path changes I think.. I am still somewhat unsure about the best way of addressing this. I'll outline my current idea and concerns that I still have, maybe you have some thoughts on it. ACLs are currently