Re: [DISCUSS] KIP-253: Support in-order message delivery with partition expansion

Hi, just want to throw my though in. In general the functionality is very usefull, we should though not try to find the architecture to hard while implementing. The manual steps would be to create a new topic the mirrormake from the new old topic to the new topic wait for mirror making to

Re: [VOTE] 1.0.1 RC2

+1 (non-binding) Built src and ran tests Ran core quick start On Sat, Feb 24, 2018 at 8:44 PM, Jakub Scholz wrote: > +1 (non-binding) ... I used the Scala 2.12 binaries and run my tests with > producers / consumers. > > On Thu, Feb 22, 2018 at 1:06 AM, Ewen Cheslack-Postava

[STREAMS] KafkaStreams.toString() deprecated?!

Hi, I've just found that KafkaStreams.toString [1] is deprecated, but I think that it does not make sense. The parameterless toString is simply part of the java.lang.Object contract and I don't think it could ever get deprecated (unless it is by Object). I think it'd be much better if the

Re: [STREAMS] KafkaStreams.toString() deprecated?!

Thanks for the feedback. You are of course right, that we cannot remove toString() -- we used the @deprecated annotation to imply that the overwrite will be removed and toString() will fall back to Object.toString() in the future and thus not provide any useful information (at least this was the

Re: [VOTE] KIP-171 - Extend Consumer Group Reset Offset for Stream Application

Hi Jorge, I agree on being consistent across our tools. Besides the kafka-consumer-groups and kafka-streams-application-reset, a couple of other classes to consider adding the --execute options for the next major release: 1. kafka-preferred-replica-elections 2. kafka-reassign-partitions 3.

about consumer offset lost

hi，i am a kafka User，i meet a question： Qustion desc： continuously consuming a topic，and invoke commitOffseSynz()，after a period of time（Time is not fixed，about one hour） it will reprocess from earliest of target topic. why? consumer config:

[jira] [Resolved] (KAFKA-4921) AssignedPartition should implement equals

[ https://issues.apache.org/jira/browse/KAFKA-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-4921. -- Resolution: Fixed Fix Version/s: 0.11.0.0 > AssignedPartition should implement equals >

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

See

[jira] [Resolved] (KAFKA-5327) Console Consumer should only poll for up to max messages

[ https://issues.apache.org/jira/browse/KAFKA-5327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-5327. Resolution: Fixed > Console Consumer should only poll for up to max messages >

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

See

Build failed in Jenkins: kafka-trunk-jdk9 #435

See Changes: [jason] KAFKA-5327; Console Consumer should not commit messages not printed -- [...truncated 1.89 MB...]

Re: [VOTE] KIP-171 - Extend Consumer Group Reset Offset for Stream Application

I agree on consistency, too. However, I am not sure if we should introduce an explicit --execute option. Anybody familiar with Linux tools will expect a command to execute by default. Thus, I would suggest to remove --execute for all tools that use this option atm. Btw: there is a related Jira:

[jira] [Resolved] (KAFKA-4920) Stamped should implement equals

[ https://issues.apache.org/jira/browse/KAFKA-4920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-4920. -- Resolution: Won't Fix > Stamped should implement equals > --- > >

Re: [STREAMS] KafkaStreams.toString() deprecated?!

Hi Matthias, That makes things so much clearer. Thanks for your help understanding the codebase better. Speaking of the code base of Kafka Streams, I've got typo fixes and docs improvements locally here and there scattered throughout the code of Kafka Streams, what are the proper steps to get

[jira] [Created] (KAFKA-6593) Coordinator disconnect in heartbeat thread can cause commitSync to block indefinitely

Jason Gustafson created KAFKA-6593: -- Summary: Coordinator disconnect in heartbeat thread can cause commitSync to block indefinitely Key: KAFKA-6593 URL: https://issues.apache.org/jira/browse/KAFKA-6593

Re: [STREAMS] KafkaStreams.toString() deprecated?!

Hello Jacek, Please see this guidance on submitting a PR; usually for typo fixes and minor doc changes, one does not need to create a JIRA but can list the PR title as "MINOR:..." or "HOTFIX: .."

KAFKA-5609

Hello Team, Have created below Pull Request for KAFKA-5609. Also am attaching the patch for reference. Jira: https://issues.apache.org/jira/browse/KAFKA-5609 PR: https://github.com/apache/kafka/pull/4619 Let me know if any more information is needed in order to merge the Pull Request. Best

Wiki permission

Hi all, Can I have permission for create and edit KIP? My profile name is Panuwat Anawatmongkhon. Cheers, Benz

[jira] [Created] (KAFKA-6595) Kafka connect commit offset incorrectly.

Hanlin Liu created KAFKA-6595: - Summary: Kafka connect commit offset incorrectly. Key: KAFKA-6595 URL: https://issues.apache.org/jira/browse/KAFKA-6595 Project: Kafka Issue Type: Bug

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

See

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

See Changes: [github] MINOR: Rename stream partition assignor to streams partition assignor -- [...truncated 415.19 KB...] kafka.server.epoch.LeaderEpochFileCacheTest >

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

See

Re: [VOTE] 1.1.0 RC0

+1 (non-binding) Built the source and ran quickstart (including streams) successfully on Ubuntu (with both Java 8 and Java 9). I understand the Windows platform is not officially supported, but I ran the same on Windows 10, and except for Step 7 (Connect) everything else worked fine. There

Re: about consumer offset lost

Does your offset commitOffseSynz() get succeeded? if your controlling offset commit, i believe you shouldn;t require auto.offset.reset=earliest. Thank you, Naresh On Mon, Feb 26, 2018 at 10:26 AM, zho...@cnsuning.com wrote: > hi，i am a kafka User，i meet a question： >

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

See Changes: [jason] KAFKA-5327; Console Consumer should not commit messages not printed -- [...truncated 243.71 KB...] kafka.api.AuthorizerIntegrationTest >

Re: [VOTE] KIP-171 - Extend Consumer Group Reset Offset for Stream Application

Hi all, Thanks for the feedback. I have updated the "Compatibility, Deprecation, and Migration Plan" section to document this to support the rollback. I probably should have handled this change, as small as it looks, as a new KIP to avoid this issue. I like Colin's idea about asking for

Re: [DISCUSS] KIP-253: Support in-order message delivery with partition expansion

Hi Dong, Please see my comments inline. Thanks, Allen On Sun, Feb 25, 2018 at 3:33 PM, Dong Lin wrote: > Hey Allen, > > Thanks for your comment. I will comment inline. > > On Thu, Feb 22, 2018 at 3:05 PM, Allen Wang > wrote: > > > Overall this

[jira] [Created] (KAFKA-6594) 第二次启动kafka是报错00000000000000000000.timeindex: 另一个程序正在使用此文件，进程无法访问。

徐兴强 created KAFKA-6594: -- Summary: 第二次启动kafka是报错.timeindex: 另一个程序正在使用此文件，进程无法访问。 Key: KAFKA-6594 URL: https://issues.apache.org/jira/browse/KAFKA-6594 Project: Kafka Issue Type: Bug

[jira] [Resolved] (KAFKA-6196) Kafka Transactional producer with broker on windows

[ https://issues.apache.org/jira/browse/KAFKA-6196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6196. Resolution: Duplicate Thanks for the patch. Marking this as a dup since it seems to be the

[jira] [Resolved] (KAFKA-6153) Kafka Transactional Messaging does not work on windows but on linux

[ https://issues.apache.org/jira/browse/KAFKA-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6153. Resolution: Duplicate Seems like the same underlying issue as KAFKA-6052. Marking as dup

[jira] [Resolved] (KAFKA-6076) Using new producer api of transaction twice failed when server run on Windows OS

[ https://issues.apache.org/jira/browse/KAFKA-6076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-6076. Resolution: Duplicate Marking as dup of KAFKA-6052 since it is likely the same underlying