[jira] [Created] (KAFKA-6821) The producer attempted to use a producer id which is not currently assigned to its transactional id

RandySun created KAFKA-6821: --- Summary: The producer attempted to use a producer id which is not currently assigned to its transactional id Key: KAFKA-6821 URL: https://issues.apache.org/jira/browse/KAFKA-6821

Re: Can I get permission to create KIP?

Hello Qingjun, I have added you to the Kafka wiki space. Cheers, Guozhang On Mon, Apr 23, 2018 at 4:21 PM, qingjun wu wrote: > Hi Dear, > > I found something that Kafka should improve. Can I get permission for this? > I am working for Microsoft actually. If you need me to login as Microsoft,

Can I get permission to create KIP?

Hi Dear, I found something that Kafka should improve. Can I get permission for this? I am working for Microsoft actually. If you need me to login as Microsoft, I can do that too. But please advice. My Login ID: WadeWu My Login Email: wuqing...@gmail.com Thank you! -- Best Regards

Jenkins build is back to normal : kafka-trunk-jdk7 #3366

See

RE: RE: [DISCUSS] KIP-280: Enhanced log compaction

That is definitely clearer, KIP updated! From: Guozhang Wang Sent: 23 April 2018 23:44 To: dev@kafka.apache.org Subject: Re: RE: [DISCUSS] KIP-280: Enhanced log compaction Thanks Luís. The KIP looks good to me. Just that what I left as a minor: `When both records being compared contain a matchin

Jenkins build is back to normal : kafka-trunk-jdk10 #43

See

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

See Changes: [wangguoz] KAFKA-6670: Implement a Scala wrapper library for Kafka Streams -- [...truncated 416.18 KB...] kafka.admin.ResetConsumerGroupOffsetTest > testRese

[jira] [Created] (KAFKA-6820) Improve on StreamsMetrics Public APIs

Guozhang Wang created KAFKA-6820: Summary: Improve on StreamsMetrics Public APIs Key: KAFKA-6820 URL: https://issues.apache.org/jira/browse/KAFKA-6820 Project: Kafka Issue Type: Improvement

[jira] [Created] (KAFKA-6819) Refactor build-in StreamsMetrics internal implementations

Guozhang Wang created KAFKA-6819: Summary: Refactor build-in StreamsMetrics internal implementations Key: KAFKA-6819 URL: https://issues.apache.org/jira/browse/KAFKA-6819 Project: Kafka Issue

Re: RE: [DISCUSS] KIP-280: Enhanced log compaction

Thanks Luís. The KIP looks good to me. Just that what I left as a minor: `When both records being compared contain a matching "compaction value", then the record with the highest offset will be kept;` I understand your intent, it's just that the sentence itself is a bit misleading, I think what y

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

See Changes: [wangguoz] KAFKA-6376; refactor skip metrics in Kafka Streams [jason] MINOR: Fix formatting in --new-consumer deprecation warning (#4903) -- [...truncated 41

RE: RE: [DISCUSS] KIP-280: Enhanced log compaction

Hello Guozhang, The KIP is now updated to reflect this choice in strategy. Please let me know your thoughts there. Kind Regards, Luís From: Guozhang Wang Sent: 23 April 2018 19:32 To: dev@kafka.apache.org Subject: Re: RE: [DISCUSS] KIP-280: Enhanced log compaction Hi Luis, I think by "generali

Build failed in Jenkins: kafka-trunk-jdk7 #3365

See Changes: [wangguoz] KAFKA-6376; refactor skip metrics in Kafka Streams [jason] MINOR: Fix formatting in --new-consumer deprecation warning (#4903) -- [...truncated 41

[jira] [Resolved] (KAFKA-6670) Implement a Scala wrapper library for Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-6670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-6670. -- Resolution: Fixed Fix Version/s: 1.2.0 Issue resolved by pull request 4756 [https://githu

Build failed in Jenkins: kafka-trunk-jdk10 #42

See Changes: [wangguoz] KAFKA-6376; refactor skip metrics in Kafka Streams [jason] MINOR: Fix formatting in --new-consumer deprecation warning (#4903) -- [...truncated 1.4

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

See Changes: [wangguoz] MINOR: Fixed deserialization.exception.handler default value of -- [...truncated 419.51 KB...] kafka.message.ByteBufferMessageSetTest > testWriteT

Jenkins build is back to normal : kafka-trunk-jdk7 #3364

See

Re: [DISCUSS] KIP-278: Add version option to Kafka's commands

FYI, the injection via the build process that is mentioned here already happens. See AppInfoParser. Ismael On Mon, Apr 23, 2018 at 9:39 AM, Colin McCabe wrote: > Hi Sasaki, > > Thanks for the KIP. I think a version flag is a good idea. > > Can you give a little more detail about what would be

Build failed in Jenkins: kafka-trunk-jdk10 #41

See Changes: [wangguoz] MINOR: Fixed deserialization.exception.handler default value of -- [...truncated 1.48 MB...] kafka.admin.ResetConsumerGroupOffsetTest > testResetOff

[jira] [Resolved] (KAFKA-6376) Improve Streams metrics for skipped records

[ https://issues.apache.org/jira/browse/KAFKA-6376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-6376. -- Resolution: Fixed Fix Version/s: 1.2.0 Issue resolved by pull request 4812 [https://githu

Re: RE: [DISCUSS] KIP-280: Enhanced log compaction

Hi Luis, I think by "generalizing it" we could go beyond numerical values, and that's why I suggested we do not need to require that the type serialized to the bytes have any numerical semantics since it has to ben serialized to a byte array anyways. I understand that for your use case, the intend

RE: RE: [DISCUSS] KIP-280: Enhanced log compaction

Hello Guozhang, Thanks for the fast reply! As for the matter of the timestamp, it’s now added to the KIP, so I hope this is correctly addressed. Kindly let me know if you would like some adaptions to the concept. bq. The issue that I do not understand completely is why you'd keep saying that

[jira] [Resolved] (KAFKA-6815) "default.production.exception.handler" default value is not specified correctly in KafkaStream doc

[ https://issues.apache.org/jira/browse/KAFKA-6815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-6815. -- Resolution: Fixed Fix Version/s: 1.0.0 1.1.0 > "default.production.exc

Re: [DISCUSS] KIP-278: Add version option to Kafka's commands

Hi Sasaki, Thanks for the KIP. I think a version flag is a good idea. Can you give a little more detail about what would be displayed when the version command was used? We clearly want the version number, but we probably also want to know if this is an official release, or a random SNAPSHOT f

Re: RE: [DISCUSS] KIP-280: Enhanced log compaction

Hello Luis, Thanks for your email, replying to your points in the following: > I don't personally see advantages in it, but also the only disadvantage that I can think of is putting multiple meanings on this field. If we do not treat timestamp as a special value of the config, then I cannot use

[jira] [Created] (KAFKA-6818) Efficient way to get last n rows via admin client

Werner Daehn created KAFKA-6818: --- Summary: Efficient way to get last n rows via admin client Key: KAFKA-6818 URL: https://issues.apache.org/jira/browse/KAFKA-6818 Project: Kafka Issue Type: Imp

Re: RE: [DISCUSS] KIP-280: Enhanced log compaction

Hi Guozhang, Thank you very much for the patience in explaining your points, I've learnt quite a bit in researching and experimenting after your replies. bq. I still think it is worth defining `timestamp` as a special compaction value I don't personally see advantages in it, but also the only

[jira] [Resolved] (KAFKA-6799) Consumer livelock during consumer group rebalance

[ https://issues.apache.org/jira/browse/KAFKA-6799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Sasvari resolved KAFKA-6799. --- Resolution: Information Provided > Consumer livelock during consumer group rebalance > ---

[jira] [Created] (KAFKA-6817) UnknownProducerIdException when writing messages with old timestamps

Odin Standal created KAFKA-6817: --- Summary: UnknownProducerIdException when writing messages with old timestamps Key: KAFKA-6817 URL: https://issues.apache.org/jira/browse/KAFKA-6817 Project: Kafka

[jira] [Created] (KAFKA-6816) Tables in documentation are truncated

Hashan Gayasri Udugahapattuwa created KAFKA-6816: Summary: Tables in documentation are truncated Key: KAFKA-6816 URL: https://issues.apache.org/jira/browse/KAFKA-6816 Project: Kafka