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

See Changes: [jason] MINOR: Use `Topic::isInternalTopic` instead of directly checking (#7047) -- [...truncated 2.96 MB...] org.apache.kafka.connect.data.ValuesTest >

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

See Changes: [cmccabe] KAFKA-: Adds RoundRobinPartitioner with tests (#6771) [jason] MINOR: Use `Topic::isInternalTopic` instead of directly checking (#7047) --

Re: [DISCUSS] KIP-213: Second follow-up on Foreign Key Joins

I know what I posted was a bit of a wall of text, but three follow up thoughts to this: 1) Is it possible to enforce exactly-once for a portion of the topology? I was trying to think about how to process my proposal with at-least-once processing (or at-most-once processing) and I came up

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

See

[jira] [Resolved] (KAFKA-8642) Send LeaveGroupRequest for static members when reaching `max.poll.interval.ms`

[ https://issues.apache.org/jira/browse/KAFKA-8642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Boyang Chen resolved KAFKA-8642. Resolution: Invalid Synced with [~hachikuji], the session timeout should always be smaller than

[VOTE] KIP-480 : Sticky Partitioner

Hello all, I'd like to start the vote for KIP-480 : Sticky Partitioner. https://cwiki.apache.org/confluence/display/KAFKA/KIP-480%3A+Sticky+Partitioner Thank you, Justine Olshan

[jira] [Created] (KAFKA-8644) The Kafka protocol generator should allow null defaults for bytes and array fields

Colin P. McCabe created KAFKA-8644: -- Summary: The Kafka protocol generator should allow null defaults for bytes and array fields Key: KAFKA-8644 URL: https://issues.apache.org/jira/browse/KAFKA-8644

[jira] [Resolved] (KAFKA-7788) Support null defaults in KAFKA-7609 RPC specifications

[ https://issues.apache.org/jira/browse/KAFKA-7788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe resolved KAFKA-7788. Resolution: Duplicate > Support null defaults in KAFKA-7609 RPC specifications >

[jira] [Created] (KAFKA-8643) Incompatible MemberDescription constructor change

Boyang Chen created KAFKA-8643: -- Summary: Incompatible MemberDescription constructor change Key: KAFKA-8643 URL: https://issues.apache.org/jira/browse/KAFKA-8643 Project: Kafka Issue Type: Bug

Re: [DISCUSS] KIP-459: Improve KafkaStreams#close

Hi Matthias, Have you thought about this issue? Thanks, Dongjin On Wed, Jun 19, 2019 at 5:07 AM Dongjin Lee wrote: > Hello. > > I just uploaded the draft implementation of the three proposed > alternatives. > > - Type A: define a close timeout constant - >

Re: [DISCUSS] KIP-482: The Kafka Protocol should Support Optional Fields

Thanks Colin for the KIP. For my own edification why are we doing this "Optional fields can have any type, except for an array of structures."? Why can't we have an array of structures? -- -Jose

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

Ah, my apologies, I must have just overlooked it. Thanks for the update, too. Just one more super-small question, do we need this variant: > New method public static Serde> ListSerde() in org.apache.kafka.common.serialization.Serdes class (infers list implementation and inner serde from config

Re: Nag!! KAFKA-8629 - Some feedback wanted

Hey Andy, Thanks for looking into this. I've been curious about it for some time. I'm glad to hear that the gap to get there is so small. You mentioned potentially switching off the JMX stuff with a config option. I'm not sure hiding the JMX features behind a config flag would be good enough...

Re: [DISCUSS] KIP-478 Strongly Typed Processor API

Ah, good catch! I didn't mean to include the for Transform itself. I must have just glossed over it when I was writing the KIP. It would apply to TransformValues, since forwarding is disabled. But for Transform, it should be bounded to the result type. The Transformer interface actually

[jira] [Created] (KAFKA-8642) Send LeaveGroupRequest for static members when reaching `max.poll.interval.ms`

Boyang Chen created KAFKA-8642: -- Summary: Send LeaveGroupRequest for static members when reaching `max.poll.interval.ms` Key: KAFKA-8642 URL: https://issues.apache.org/jira/browse/KAFKA-8642 Project:

Re: Nag!! KAFKA-8629 - Some feedback wanted

I think it would be awesome to support GraalVM native images for Kafka Streams and CLI tools. Ismael On Tue, Jul 9, 2019, 12:40 PM Andy Muir wrote: > Hi > > I hope you can have a look at > https://issues.apache.org/jira/browse/KAFKA-8629 < > https://issues.apache.org/jira/browse/KAFKA-8629>

Re: Nag!! KAFKA-8629 - Some feedback wanted

Hi Andy Can you elaborate on two things for clarity’s sake? 1) Are there any alternatives we can use for JMX instead of commenting it out? 2) Are there any other limitations with Graal VM that may impede future development? The second one is more difficult to answer I suspect because it

Nag!! KAFKA-8629 - Some feedback wanted

Hi I hope you can have a look at https://issues.apache.org/jira/browse/KAFKA-8629 and perhaps give me some feedback? I’d like to decide if this is worth pursuing! I believe that making apps built on top of Kafka Streams can benefit hugely

Re: [DISCUSS] KIP-435: Internal Partition Reassignment Batching

Hey Viktor, I think it is intuitive if there are on a global level...If we applied > them on every batch then we > couldn't really guarantee any limits as the user would be able to get > around it with submitting lots of reassignments. Agreed. Could we mention this explicitly in the KIP? Also

Re: [DISCUSS] KIP-480 : Sticky Partitioner

Hi M, The RoundRobinPartitioner added by KIP-369 doesn't interact with this KIP. If you configure your producer to use RoundRobinPartitioner, then the DefaultPartitioner will not be used. And the "sticky" behavior is implemented only in the DefaultPartitioner. regards, Colin On Tue, Jul

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

See Changes: [manikumar.reddy] MINOR: Fixes AK config typos (#7046) -- [...truncated 2.55 MB...] org.apache.kafka.connect.transforms.TimestampConverterTest >

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

See

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

See Changes: [jason] KAFKA-8591; WorkerConfigTransformer NPE on connector configuration -- [...truncated 6.46 MB...] kafka.security.auth.ZkAuthorizationTest >

Jenkins build is back to normal : kafka-2.3-jdk8 #58

See

Re: [DISCUSS] KIP-480 : Sticky Partitioner

Hello Justine, I have one item I wanted to discuss. We are currently in review stage for KAFKA- where we can choose always RoundRobin regardless of null/usable key. If I understood this KIP motivation correctly, you are still honouring how the hashing of key works for DefaultPartitioner.

Re: PR review

Hello Colin, I appreciate the time for reviewing this PR. I have now incorporated your (and Matthias's) comments and the PR has been resubmitted. Please let me know if there is more that we need to change. Thanks again, On Mon, 8 Jul 2019 at 23:50, Colin McCabe wrote: > Hi M. Manna, > > I

Re: [DISCUSS] KIP-455 Create an Admin API for Replica Reassignments

Hey there everybody, I've edited the KIP. Here is a diff of the changes - https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=112820260=13=11 Specifically, - new AdminAPI for listing ongoing reassignments for _a given list of topics_. - made

[jira] [Created] (KAFKA-8641) Invalid value ogg_kafka_test_key for configuration value.deserializer: Class ogg_kafka_test_key could not be found.

chen qiang created KAFKA-8641: - Summary: Invalid value ogg_kafka_test_key for configuration value.deserializer: Class ogg_kafka_test_key could not be found. Key: KAFKA-8641 URL:

Build failed in Jenkins: kafka-2.2-jdk8 #144

See Changes: [jason] KAFKA-8591; WorkerConfigTransformer NPE on connector configuration -- [...truncated 1.92 MB...] kafka.security.auth.ZkAuthorizationTest >

Re: [DISCUSS] KIP-221: Repartition Topic Hints in Streams

Hello, In order to move this KIP forward, I’ve updated confluence page with the new proposal https://cwiki.apache.org/confluence/display/KAFKA/KIP-221%3A+Enhance+KStream+with+Connecting+Topic+Creation+and+Repartition+Hint

[jira] [Resolved] (KAFKA-8591) NPE when reloading connector configuration using WorkerConfigTransformer

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