[jira] [Reopened] (KAFKA-9859) kafka-streams-application-reset tool doesn't take into account topics generated by KTable foreign key join operation

[ https://issues.apache.org/jira/browse/KAFKA-9859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Levani Kokhreidze reopened KAFKA-9859: -- > kafka-streams-application-reset tool doesn't take into account topics > generated by KTa

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

See Changes: [github] MINOR: equals() should compare all fields for generated classes (#8539) -- [...truncated 3.03 MB...] org.apache.kafka.streams.TopologyTestDriverTes

Build failed in Jenkins: kafka-2.4-jdk8 #190

See Changes: [rhauch] KAFKA-9883: Add better error message when REST API forwards a request -- [...truncated 7.04 MB...] org.apache.kafka.connect.transforms.TimestampConvert

[DISCUSS] KIP-598: Augment TopologyDescription with store and source / sink serde information

Hello folks, I'd like to start the discussion for KIP-598: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=148648762 It proposes to augment the topology description's sub-classes with store and source / sink serde information. Let me know what you think, thanks! -- -- Guozhang

Re: [DISCUSS] KIP-553: Enable TLSv1.3 by default and disable all protocols except [TLSV1.2, TLSV1.3]

Hi Nikolay, Seems like we have been able to run the system tests with TLS 1.3. Do we run them nightly? Ismael On Fri, Feb 14, 2020 at 4:17 AM Nikolay Izhikov wrote: > Hello, Kafka team. > > I ran system tests that use SSL for the TLSv1.3. > You can find the results of the tests in the Jira tic

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

See Changes: [github] MINOR: equals() should compare all fields for generated classes (#8539) -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node env

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

See

Jenkins build is back to normal : kafka-trunk-jdk14 #15

See

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

See Changes: [github] KAFKA-9823: Remember the sent generation for the coordinator request [github] KAFKA-9844; Fix race condition which allows more than maximum number of -

Re: [VOTE] KIP-594: Expose output topic names from TopologyTestDriver

Vote is: +4 binding for, no against. Thanks all! On Thu, 23 Apr 2020 at 22:05, Guozhang Wang wrote: > +1. Thanks Andy! > > > Guozhang > > On Thu, Apr 23, 2020 at 6:53 AM Bill Bejeck wrote: > > > Hi Andy, > > > > Thanks for the KIP. It's a + 1(binding) for me. > > > > -Bill > > > > On Thu, A

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

See Changes: [github] KAFKA-9883: Add better error message when REST API forwards a request [github] KAFKA-9823: Remember the sent generation for the coordinator request --

Re: [DISCUSS] KIP-597: MirrorMaker2 internal topics Formatters

Hi Mickael, The KIP looks great and the additional formatters seem like excellent tools for debugging and diving into the internals of Mirror Maker 2.0. I've got a few thoughts on the proposed changes: 1. Would it be possible to provide examples for what the actual output might look like when the

Build failed in Jenkins: kafka-trunk-jdk14 #14

See Changes: [github] KAFKA-9883: Add better error message when REST API forwards a request [github] KAFKA-9823: Remember the sent generation for the coordinator request

[jira] [Resolved] (KAFKA-9883) Connect request to restart task can result in IllegalArgumentError: "uriTemplate" parameter is null

[ https://issues.apache.org/jira/browse/KAFKA-9883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-9883. -- Resolution: Fixed > Connect request to restart task can result in IllegalArgumentError: > "uri

Re: [VOTE] KIP-594: Expose output topic names from TopologyTestDriver

+1. Thanks Andy! Guozhang On Thu, Apr 23, 2020 at 6:53 AM Bill Bejeck wrote: > Hi Andy, > > Thanks for the KIP. It's a + 1(binding) for me. > > -Bill > > On Thu, Apr 23, 2020 at 9:45 AM John Roesler wrote: > > > Hi Andy, > > > > I just took another look, and it looks good to me! Thanks for t

Re: [VOTE] KIP-594: Expose output topic names from TopologyTestDriver

> Dump I hope you intended to "bump" the vote thread but not "dump the KIP" :D +1 (binding) -Matthias On 4/23/20 6:53 AM, Bill Bejeck wrote: > Hi Andy, > > Thanks for the KIP. It's a + 1(binding) for me. > > -Bill > > On Thu, Apr 23, 2020 at 9:45 AM John Roesler wrote: > >> Hi And

Re: [DISCUSS] KIP-594: Expose output topic names from TopologyTestDriver

Thanks Andi! I buy your argument. For exposing topics names via `TopologyDescription` I create a JIRA for tracking: https://issues.apache.org/jira/browse/KAFKA-9913 -Matthias On 4/20/20 8:07 AM, Andy Coates wrote: > Hey all, > >> One other point, I’m actually mildly concerned about what you sa

[jira] [Created] (KAFKA-9913) TopologyDescription should expose all topic name progrematically

Matthias J. Sax created KAFKA-9913: -- Summary: TopologyDescription should expose all topic name progrematically Key: KAFKA-9913 URL: https://issues.apache.org/jira/browse/KAFKA-9913 Project: Kafka

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

See Changes: [github] KAFKA-9883: Add better error message when REST API forwards a request -- [...truncated 3.01 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

[jira] [Created] (KAFKA-9912) Kafka deletes full log on startup written 30mins ago - wrongly claims retention time 7d breach

Igor Baltiyskiy created KAFKA-9912: -- Summary: Kafka deletes full log on startup written 30mins ago - wrongly claims retention time 7d breach Key: KAFKA-9912 URL: https://issues.apache.org/jira/browse/KAFKA-9912

[jira] [Resolved] (KAFKA-9844) Maximum number of members within a group is not always enforced due to a race condition in join group

[ https://issues.apache.org/jira/browse/KAFKA-9844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9844. Fix Version/s: 2.6.0 Resolution: Fixed > Maximum number of members within a group is

[jira] [Created] (KAFKA-9910) Implement new transaction timed out error

Boyang Chen created KAFKA-9910: -- Summary: Implement new transaction timed out error Key: KAFKA-9910 URL: https://issues.apache.org/jira/browse/KAFKA-9910 Project: Kafka Issue Type: Sub-task

[jira] [Created] (KAFKA-9911) Implement new producer fenced error

Boyang Chen created KAFKA-9911: -- Summary: Implement new producer fenced error Key: KAFKA-9911 URL: https://issues.apache.org/jira/browse/KAFKA-9911 Project: Kafka Issue Type: Sub-task

Jenkins build is back to normal : kafka-trunk-jdk14 #13

See

[jira] [Resolved] (KAFKA-9823) Consumer should check equality of the generation for coordinator requests

[ https://issues.apache.org/jira/browse/KAFKA-9823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-9823. -- Fix Version/s: 2.6.0 Resolution: Fixed > Consumer should check equality of the generatio

Re: [VOTE] KIP-584: Versioning scheme for features

Hi Kowshik, Thanks again for working on this-- it looks great. I went over the KIP again and have a few more comments. === It would be good to note that deprecating a feature version (in other words, increasing minVersionLevel on the broker) is an incompatible change, which requires a major

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

See

Re: [DISCUSSION] KIP-418: A method-chaining way to branch KStream

Hi Ivan, Welcome back! Thanks for the update. This KIP looks really nice. Thanks also for taking into account the grammar. I think you’ve done a good job of balancing the proposed grammar’s objectives with the current API’s idioms. I have just a few comments remaining: 1. Can you propose to

Build failed in Jenkins: kafka-trunk-jdk14 #12

See Changes: [github] MINOR: Some html fixes in Streams DSL documentation (#8503) -- [...truncated 6.05 MB...] org.apache.kafka.streams.test.OutputVerifierTest > shouldPa

Re: [DISCUSS] KIP-590: Redirect Zookeeper Mutation Protocols to The Controller

Thanks all, IIUC, the necessity of doing the audit log on the controller side is because we need to make sure the authorized resource modifications eventually arrive on the target broker side, but is that really necessary? I'm thinking the possibility of doing the audit log on the forwarding brok

[jira] [Resolved] (KAFKA-9907) Switch default build to Scala 2.13

[ https://issues.apache.org/jira/browse/KAFKA-9907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-9907. Resolution: Fixed > Switch default build to Scala 2.13 > -- > >

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

See Changes: [github] KAFKA-9907: Switch default build to Scala 2.13 (#8537) -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variable

Re: [DISCUSS] KIP-590: Redirect Zookeeper Mutation Protocols to The Controller

I agree that this would be useful to have and shouldn't create issues in 99% of all cases. But it would be a breaking change to a public API. I had a quick look at the two large projects that come to mind which might be affected: Ranger and Sentry - both seem to operate directly with KafkaPrincipal

Re: [VOTE] KIP-594: Expose output topic names from TopologyTestDriver

Hi Andy, Thanks for the KIP. It's a + 1(binding) for me. -Bill On Thu, Apr 23, 2020 at 9:45 AM John Roesler wrote: > Hi Andy, > > I just took another look, and it looks good to me! Thanks for the > contribution. > > I’m +1 (binding) > > -John > > On Thu, Apr 23, 2020, at 06:49, Andy Coates wr

Re: [VOTE] KIP-594: Expose output topic names from TopologyTestDriver

Hi Andy, I just took another look, and it looks good to me! Thanks for the contribution. I’m +1 (binding) -John On Thu, Apr 23, 2020, at 06:49, Andy Coates wrote: > Dump > > On Thu, 16 Apr 2020 at 00:48, Andy Coates wrote: > > > Hey all, > > > > I would like to start the vote for KIP-

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

See Changes: [github] MINOR: Enable fatal warnings with scala 2.13 (#8429) [github] MINOR: Some html fixes in Streams DSL documentation (#8503) -- [...truncated 3.02 MB

Re: [DISCUSS] KIP-590: Redirect Zookeeper Mutation Protocols to The Controller

Hmm... Maybe we need to add some way to serialize and deserialize KafkaPrincipal subclasses to/from string. We could add a method to KafkaPrincipalBuilder#deserialize and a method KafkaPrincipal#serialize, I suppose. best, Colin On Thu, Apr 23, 2020, at 02:14, Tom Bentley wrote: > Hi folks,

Build failed in Jenkins: kafka-trunk-jdk14 #11

See Changes: [github] MINOR: Downgrade test should wait for ISR rejoin between rolls (#8495) [github] KAFKA-9852: Change the max duration that calls to the buffer pool can [github] MINOR: Enable fatal warnings w

Re: [VOTE] KIP-594: Expose output topic names from TopologyTestDriver

Dump On Thu, 16 Apr 2020 at 00:48, Andy Coates wrote: > Hey all, > > I would like to start the vote for KIP- > 594 > >

[jira] [Created] (KAFKA-9909) Kafka Streams : offset control to Streams API

Gopikrishna created KAFKA-9909: -- Summary: Kafka Streams : offset control to Streams API Key: KAFKA-9909 URL: https://issues.apache.org/jira/browse/KAFKA-9909 Project: Kafka Issue Type: Improveme

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

See

[jira] [Created] (KAFKA-9908) Kafka client always trying "kinit -R" even the ticketCache has been renewed by external

Bob Wen created KAFKA-9908: -- Summary: Kafka client always trying "kinit -R" even the ticketCache has been renewed by external Key: KAFKA-9908 URL: https://issues.apache.org/jira/browse/KAFKA-9908 Project: Ka

Re: [DISCUSS] KIP-590: Redirect Zookeeper Mutation Protocols to The Controller

Hi folks, Colin wrote: > The final broker knows it can trust the principal name in the envelope > (since EnvelopeRequest requires CLUSTERACTION on CLUSTER). So it can use > that principal name for authorization (given who you are, what can you > do?) The forwarded principal name will also be us