Re: [DISCUSS] KIP-174 - Deprecate and remove internal converter configs in WorkerConfig

Thanks Ewen, and apologies as I missed this too. I'll start vote for this soon and proceed for the next steps. On Fri, 5 Jan 2018 at 09:03 Ewen Cheslack-Postava wrote: > Sorry I lost track of this thread. If things are in good shape we should > probably vote on this and get the deprecation commi

[jira] [Created] (KAFKA-6425) Calculating cleanBytes in LogToClean might not be correct

huxihx created KAFKA-6425: - Summary: Calculating cleanBytes in LogToClean might not be correct Key: KAFKA-6425 URL: https://issues.apache.org/jira/browse/KAFKA-6425 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-6426) Kafka SASL/SCRAM authentication does not fail for incorrect username or password.

Menaka Madushanka created KAFKA-6426: Summary: Kafka SASL/SCRAM authentication does not fail for incorrect username or password. Key: KAFKA-6426 URL: https://issues.apache.org/jira/browse/KAFKA-6426

Re: [DISCUSS] KIP 145 - Expose Record Headers in Kafka Connect

I’d agree with Ewen on the point of conversions, this I think is a feature not bound to headers, and should move to some other place. The connect header object in my view should simply expose: key: String value: Object valueSchema: Schema So its much more inline with the ConnectRecord, and woul

Re: [VOTE] KIP-226 - Dynamic Broker Configuration

Hi Jun, We are using 2-way encryption. The password configs encoded are keystore/truststore passwords and JAAS configuration. We need to be able to extract the actual values for these, so we cannot use 1-way hash. So if we have the old secret, we can decrypt and get the original values. Thank you

[jira] [Resolved] (KAFKA-6077) Let SimpleConsumer support Kerberos authentication

[ https://issues.apache.org/jira/browse/KAFKA-6077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-6077. -- Resolution: Won't Fix The old consumer is no longer supported, please consider above mentioned options.

Consumer client not able to receive messages when one of broker is pushed down in the cluster

Hi, I have a Apache kafka cluster with 3 nodes(say 1,2,3) with replication factor of 3 and partitions as 3. When my producer client, consumer client and the cluster are running, able to transfer messages from producer to consumer without any issues. Now I stopped leader node say node 1 from the

Related queue

Greetings, I would like to ask you very simple question. Does Kajfa provide something called Related queues? By this term we mean if it possible to set Kafka on server 1 and service which will fill Kafka with data will be on server 2. Consumers are on servers 3, 4 . N. Now imagine that th

Re: [DISCUSS] KIP-212: Enforce set of legal characters for connector names

Sönke, I'm happy with the current proposal. Ewen, the proposal allows any characters in the name as long as they are properly escaped/encoded. That seems to adhere to the robustness principle. The only exception is that the proposal trims leading and trailing whitespace characters in an attempt to

[jira] [Created] (KAFKA-6427) Inconsistent exception type from KafkaConsumer.position

Jay Kahrman created KAFKA-6427: -- Summary: Inconsistent exception type from KafkaConsumer.position Key: KAFKA-6427 URL: https://issues.apache.org/jira/browse/KAFKA-6427 Project: Kafka Issue Type:

Jenkins build is back to normal : kafka-trunk-jdk9 #291

See

Re: [DISCUSS] KIP-232: Detect outdated metadata by adding ControllerMetadataEpoch field

Hi Dong, Sorry for the late reply. I think the latest revision is looking good. I have a few minor suggestions: 1. The name "partition_epoch" makes me think it changes independently at the partition level, but all partitions for a topic should have the same epoch. Maybe "topic_epoch" is nearer th

Re: [DISCUSS] KIP-232: Detect outdated metadata by adding ControllerMetadataEpoch field

Hey Jason, Thanks a lot for the comments. I will comment inline. And I have updated the KIP accordingly. Could you take another look? On Fri, Jan 5, 2018 at 11:15 AM, Jason Gustafson wrote: > Hi Dong, > > Sorry for the late reply. I think the latest revision is looking good. I > have a few mino

[jira] [Resolved] (KAFKA-4335) FileStreamSource Connector not working for large files (~ 1GB)

[ https://issues.apache.org/jira/browse/KAFKA-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-4335. -- Resolution: Fixed Fix Version/s: 1.1.0 Issue resolved by pull request 435

[jira] [Created] (KAFKA-6428) Fail builds on findbugs warnings

Ewen Cheslack-Postava created KAFKA-6428: Summary: Fail builds on findbugs warnings Key: KAFKA-6428 URL: https://issues.apache.org/jira/browse/KAFKA-6428 Project: Kafka Issue Type: Im

[jira] [Resolved] (KAFKA-6252) A metric named 'XX' already exists, can't register another one.

[ https://issues.apache.org/jira/browse/KAFKA-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-6252. -- Resolution: Fixed Reviewer: Ewen Cheslack-Postava > A metric named 'XX' al

Build failed in Jenkins: kafka-1.0-jdk7 #119

See Changes: [me] KAFKA-6252; Close the metric group to clean up any existing metrics -- [...truncated 371.82 KB...] kafka.log.BrokerCompressionTest > testBrokerSideCompress

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

See Changes: [me] KAFKA-6252; Close the metric group to clean up any existing metrics -- [...truncated 400.97 KB...] kafka.utils.CoreUtilsTest > testReadInt STARTED kafk