[jira] [Created] (KAFKA-8706) Kafka 2.3.0 Unit Test Failures on Oracle Linux 7.2 - Need help debugging framework or issue.

Chandrasekhar created KAFKA-8706: Summary: Kafka 2.3.0 Unit Test Failures on Oracle Linux 7.2 - Need help debugging framework or issue. Key: KAFKA-8706 URL: https://issues.apache.org/jira/browse/KAFKA-8706

[jira] [Created] (KAFKA-8705) NullPointerException was thrown by topology optimization when two MergeNodes have common KeyChaingingNode

Hiroshi Nakahara created KAFKA-8705: --- Summary: NullPointerException was thrown by topology optimization when two MergeNodes have common KeyChaingingNode Key: KAFKA-8705 URL:

[jira] [Created] (KAFKA-8704) Add PartitionAssignor adapter for backwards compatibility

Sophie Blee-Goldman created KAFKA-8704: -- Summary: Add PartitionAssignor adapter for backwards compatibility Key: KAFKA-8704 URL: https://issues.apache.org/jira/browse/KAFKA-8704 Project: Kafka

[jira] [Created] (KAFKA-8703) Move PartitionAssignor to public API

Sophie Blee-Goldman created KAFKA-8703: -- Summary: Move PartitionAssignor to public API Key: KAFKA-8703 URL: https://issues.apache.org/jira/browse/KAFKA-8703 Project: Kafka Issue Type:

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

>> Just to make sure I understand the problem you're highlighting: >> I guess the difference is that the serializer and deserializer that are >> nested inside the serde also need to be configured? So, by default I'd have >> to specify all six configs when I'm using Streams? That is not the

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

See

Re: KIP-382 + Kafka Streams Question

Adam, I think we are converging :) > "userEntity"...where I only want the latest emailAddress (basic materialization) to send an email on account password update. Yes, you want all "userEntity" data on both clusters. Each cluster will have "userEntity" and the remote counterpart

[jira] [Resolved] (KAFKA-8675) "Main" consumers are not unsubsribed on KafkaStreams.close()

[ https://issues.apache.org/jira/browse/KAFKA-8675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-8675. -- Resolution: Not A Problem > "Main" consumers are not unsubsribed on KafkaStreams.close() >

Re: [VOTE] KIP-478 Strongly Typed Streams Processor API

Hi John, I left another question regarding Transformer in the DISCUSS thread. Other than that I think this KIP is ready. Thanks! Guozhang On Tue, Jul 16, 2019 at 9:01 AM John Roesler wrote: > Hi Dev, > > After a good discussion, I'd like to start the vote for KIP-478 >

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

Hi John, Just a wild thought about Transformer: now with the new Processor#init(ProcessorContext), do we still need a Transformer (and even ValueTransformer / ValueTransformerWithKey)? What if: * We just make KStream#transform to get a ProcessorSupplier as well, and inside `process()` we check

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

See Changes: [jason] KAFKA-8526; Fallback to other log dirs after getOrCreateLog failure -- [...truncated 2.57 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

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

Hello, Thanks all for your feedback. I started voting procedure for this KIP. If there’re any other concerns about this KIP, please let me know. Regards, Levani > On Jul 20, 2019, at 8:39 PM, Levani Kokhreidze wrote: > > Hi Matthias, > > Thanks for the suggestion, makes sense. > I’ve

[VOTE] KIP-221: Enhance KStream with Connecting Topic Creation and Repartition Hint

Hello, I’d like to initialize voting on KIP-221: https://cwiki.apache.org/confluence/display/KAFKA/KIP-221%3A+Enhance+KStream+with+Connecting+Topic+Creation+and+Repartition+Hint

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

Hmm, that's a tricky situation. I think Daniyar was on the right track... Producer only cares about serializer configs, and Consumer only cares about deserializer configs. I didn't see the problem with your proposal: ProducerConfig: > list.key/value.serializer.type >

[jira] [Created] (KAFKA-8702) Kafka leader election doesn't happen when leader broker port is partitioned off the network

Andrey Falko created KAFKA-8702: --- Summary: Kafka leader election doesn't happen when leader broker port is partitioned off the network Key: KAFKA-8702 URL: https://issues.apache.org/jira/browse/KAFKA-8702

Re: [DISCUSS] KIP-444: Augment Metrics for Kafka Streams

Thanks for the KIP Guozhang. I just re-read the wiki page and the DISCUSS thread. Overall LGTM. The only nit is the naming of the new config values. With AK 2.3 being released the versions numbers needs to be updated. Additionally, I actually think that "2.2-" and "2.3" are not the best names:

Re: Monitoring streams

Hello Brian, I think your main question is to distinguish 1) broker is alive but there's no new data coming into the source topics to process, and 2) broker is not alive and hence nothing is readable, in your monitoring system. I agree that currently process-rate / last-record-timestamp cannot

[jira] [Resolved] (KAFKA-6708) Review Exception messages with regards to Serde Useage

[ https://issues.apache.org/jira/browse/KAFKA-6708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-6708. Resolution: Duplicate > Review Exception messages with regards to Serde Useage >

Re: KIP-382 + Kafka Streams Question

Hi Ryanne Thanks for the clarifications! Here is one of my own, as I think it's the biggest stumbling block in my description: *> What is "table" exactly? I am interpreting this as a KTable changelog topic* "table" is not a KTable changelog topic, but simply entity data that is to be

[DISCUSS] KIP-496: Administrative API to delete consumer offsets

Hi All, I have a short KIP to add an api for consumer offset deletion: https://cwiki.apache.org/confluence/display/KAFKA/KIP-496%3A+Administrative+API+to+delete+consumer+offsets. Please take a look and let me know what you think. Thanks, Jason

[jira] [Created] (KAFKA-8701) Flaky Test SaslSslAdminClientIntegrationTest#testDescribeConfigsForTopic

Matthias J. Sax created KAFKA-8701: -- Summary: Flaky Test SaslSslAdminClientIntegrationTest#testDescribeConfigsForTopic Key: KAFKA-8701 URL: https://issues.apache.org/jira/browse/KAFKA-8701 Project:

Re: KIP-382 + Kafka Streams Question

Adam, > I think we have inconsistent definitions of Active-Active Yes, this terminology gets thrown around a lot. IMO "active" means both producers and consumers are using a cluster under normal operation -- not just during outages, and not just by something like MM2. (Obviously, MM2 has

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

Bump > On Jul 22, 2019, at 11:26 AM, Development wrote: > > Hey Matthias, > > It looks a little confusing, but I don’t have enough expertise to judge on > the configuration placement. > > If you think, it is fine I’ll go ahead with this approach. > > Best, > Daniyar Yeralin > >> On Jul 19,

Re: JIRA and KIP contributor permissions

Done. On 7/23/19 4:56 AM, Alexandre Dupriez wrote: > Hello Matthias, > > Thanks for the quick reply, I can confirm I am able to auto-assign JIRA > tickets. > > Please find here my Confluence username: alexandre.dupriez > > Many thanks, > Alexandre > > Le mar. 23 juil. 2019 à 04:38, Matthias

[jira] [Created] (KAFKA-8700) Flaky Test QueryableStateIntegrationTest#queryOnRebalance

Matthias J. Sax created KAFKA-8700: -- Summary: Flaky Test QueryableStateIntegrationTest#queryOnRebalance Key: KAFKA-8700 URL: https://issues.apache.org/jira/browse/KAFKA-8700 Project: Kafka

[jira] [Resolved] (KAFKA-8526) Broker may select a failed dir for new replica even in the presence of other live dirs

[ https://issues.apache.org/jira/browse/KAFKA-8526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-8526. Resolution: Fixed Fix Version/s: 2.4.0 > Broker may select a failed dir for new

Re: KIP-382 + Kafka Streams Question

Hi Ryanne I think we have inconsistent definitions of Active-Active. The producer is only producing to one cluster (primary) and one topic (topic "table"), and the other cluster (secondary) contains only a replication of the data via MM2 ("primary.table"). What you seemed to be proposing is that

Kafka consumer is not reading some partition

Hello. I was using Kafka 2.1.1 and facing a problem where our consumers sometimes intermittently stop consuming from one or two of the partitions. My config

[jira] [Created] (KAFKA-8699) rack aware replica, found rack with twi replicas

abdessamad created KAFKA-8699: - Summary: rack aware replica, found rack with twi replicas Key: KAFKA-8699 URL: https://issues.apache.org/jira/browse/KAFKA-8699 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-8698) ListOffsets Response protocol documentation

Fábio Silva created KAFKA-8698: -- Summary: ListOffsets Response protocol documentation Key: KAFKA-8698 URL: https://issues.apache.org/jira/browse/KAFKA-8698 Project: Kafka Issue Type: Bug

Re: JIRA and KIP contributor permissions

Hello Matthias, Thanks for the quick reply, I can confirm I am able to auto-assign JIRA tickets. Please find here my Confluence username: alexandre.dupriez Many thanks, Alexandre Le mar. 23 juil. 2019 à 04:38, Matthias J. Sax a écrit : > Hi Alexandre, > > I added you to the list of

Re: [DISCUSS] KIP-490: log when consumer groups lose a message because offset has been deleted

Jose, How do you differentiate the compaction topics from the time retention topics? Deleting a message due to compaction policy is a valid case and users won't be interested in monitoring/reading those deleted messages. Thanks, Kamal On Tue, Jul 23, 2019 at 4:00 AM Jose M wrote: > Hi

KAFKA-1194: The Kafka Broker can't delete old log files on Windows

Hello community, As I can see this issue has been long here: https://issues.apache.org/jira/browse/KAFKA-1194 which is about the Kafka logs on Windows which can't be deleted. Also, I see there is on going PR here for it: https://github.com/apache/kafka/pull/6329, but not much going there after

[jira] [Created] (KAFKA-8697) Kafka consumer group auto removal

Pavel Rogovoy created KAFKA-8697: Summary: Kafka consumer group auto removal Key: KAFKA-8697 URL: https://issues.apache.org/jira/browse/KAFKA-8697 Project: Kafka Issue Type: Improvement

[jira] [Resolved] (KAFKA-8380) We can not create a topic, immediately write to it and then read.

[ https://issues.apache.org/jira/browse/KAFKA-8380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Narendra Kumar resolved KAFKA-8380. --- Resolution: Not A Problem > We can not create a topic, immediately write to it and then

Build failed in Jenkins: kafka-2.3-jdk8 #77

See Changes: [jason] KAFKA-8678; Fix leave group protocol bug in throttling and error -- [...truncated 2.73 MB...] kafka.controller.ReplicaStateMachineTest >

[DISCUSS] KIP-495: Dynamically Adjust Log Levels in Connect

Hi everyone. I'd like to propose the following KIP to implement changing log levels on the fly in Connect workers: https://cwiki.apache.org/confluence/display/KAFKA/KIP-495%3A+Dynamically+Adjust+Log+Levels+in+Connect Would like to hear your thoughts on this. Thanks very much, Arjun