[VOTE] KIP-617: Allow Kafka Streams State Stores to be iterated backwards
Hi everyone, I'd like to start a vote on KIP-617: Allow Kafka Streams State Stores to be iterated backwards. KIP wiki page: https://cwiki.apache.org/confluence/display/KAFKA/KIP-617%3A+Allow+Kafka+Streams+State+Stores+to+be+iterated+backwards Discussion thread is here as well: https://mail-archives.apache.org/mod_mbox/kafka-dev/202005.mbox/%3cb273c113-5062-dd92-6901-21abba090...@gmail.com%3e Many thanks! Jorge. 0x5F2C6E22064982DF.asc Description: application/pgp-keys
Re: [DISCUSS] KIP-617: Allow Kafka Streams State Stores to be iterated backwards
ay >>> we should do what's right rather than maintain compatibility with >> existing >>> bugs, but sometimes there's a reasonable middle ground. >>> >>> On Tue, May 19, 2020 at 6:15 PM John Roesler >> wrote: >>>> Thanks Sophie, >>>> >>>> Woah, that’s a nasty bug. Rather than working around it, I think we >> should >>>> just fix it. I’ll leave some comments on the Jira. >>>> >>>> It doesn’t seem like it should be this KIP’s concern that some serdes >>>> might be incorrectly written. >>>> >>>> Were there other practical concerns that you had in mind? >>>> >>>> Thanks, >>>> John >>>> >>>> On Tue, May 19, 2020, at 19:10, Sophie Blee-Goldman wrote: >>>>> I like this "fancy idea" to just flip the to/from bytes but I think >> there >>>>> are some practical limitations to implementing this. In particular >>>>> I'm thinking about this issue >>>>> <https://issues.apache.org/jira/browse/KAFKA-8159> with the built-in >>>> signed >>>>> number serdes. >>>>> >>>>> This trick would actually fix the problem for negative-negative >> queries >>>>> (ie where to & from are negative) but would cause undetectable >>>>> incorrect results for negative-positive queries. For example, say you >>>>> call #range with from = -1 and to = 1, using the Short serdes. The >>>>> serialized bytes for that are >>>>> >>>>> from = >>>>> to = 0001 >>>>> >>>>> so we would end up flipping those and iterating over all keys from >>>>> 0001 to . Iterating in lexicographical >>>>> order means we would iterate over every key in the space *except* for >>>>> 0, but 0 is actually the *only* other key we meant to be included in >> the >>>>> range query. >>>>> >>>>> Currently we just log a warning and return an empty iterator when >>>>> to < from, which is obviously also incorrect but feels slightly more >>>>> palatable. If we start automatically converting to reverse queries we >>>>> can't even log a warning in this case unless we wanted to log a >> warning >>>>> every time, which would be weird to do for a valid usage of a new >>>>> feature. >>>>> >>>>> All that said, I still like the idea overall. Off the top of my head >> I >>>> guess >>>>> we could add a store config to enable/disable automatic reverse >>>> iteration, >>>>> which is off by default? >>>>> >>>>> Thanks for the KIP! This will be a nice addition >>>>> >>>>> Sophie >>>>> >>>>> >>>>> On Tue, May 19, 2020 at 3:21 PM John Roesler >>>> wrote: >>>>>> Hi there Jorge, >>>>>> >>>>>> Thanks for the KIP! >>>>>> >>>>>> I think this feature sounds very reasonable. >>>>>> >>>>>> I'm not 100% sure if this is "too fancy", but what do you think >>>>>> about avoiding the enum by instead allowing people to flip >>>>>> the "from" and "to" endpoints? I.e., reading from "A" to "Z" would >>>>>> be a forward scan, and from "Z" to "A" would be a backward one? >>>>>> >>>>>> Thanks, >>>>>> -John >>>>>> >>>>>> On Tue, May 19, 2020, at 16:20, Jorge Quilcate wrote: >>>>>>> Hi everyone, >>>>>>> >>>>>>> I would like to start the discussion for KIP-617: >>>>>>> >> https://cwiki.apache.org/confluence/display/KAFKA/KIP-617%3A+Allow+Kafka+Streams+State+Stores+to+be+iterated+backwards >>>>>>> Looking forward to your feedback. >>>>>>> >>>>>>> Thanks! >>>>>>> Jorge. >>>>>>> >>>>>>> >>>>>>> Attachments: >>>>>>> * 0x5F2C6E22064982DF.asc 0x5F2C6E22064982DF.asc Description: application/pgp-keys
[DISCUSS] KIP-617: Allow Kafka Streams State Stores to be iterated backwards
Hi everyone, I would like to start the discussion for KIP-617: https://cwiki.apache.org/confluence/display/KAFKA/KIP-617%3A+Allow+Kafka+Streams+State+Stores+to+be+iterated+backwards Looking forward to your feedback. Thanks! Jorge. 0x5F2C6E22064982DF.asc Description: application/pgp-keys
Re: [ANNOUNCE] New Kafka PMC member: Matthias J. Sax
Congrats Matthias!! On 4/19/19 11:28 AM, Mickael Maison wrote: Congrats Matthias! On Fri, Apr 19, 2019 at 6:07 AM Vahid Hashemian wrote: Congratulations Matthias! --Vahid On Thu, Apr 18, 2019 at 9:39 PM Manikumar wrote: Congrats Matthias!. well deserved. On Fri, Apr 19, 2019 at 7:44 AM Dong Lin wrote: Congratulations Matthias! Very well deserved! On Thu, Apr 18, 2019 at 2:35 PM Guozhang Wang wrote: Hello Everyone, I'm glad to announce that Matthias J. Sax is now a member of Kafka PMC. Matthias has been a committer since Jan. 2018, and since then he continued to be active in the community and made significant contributions the project. Congratulations to Matthias! -- Guozhang -- Thanks! --Vahid
[jira] [Created] (KAFKA-6938) Add documentation for accessing Headers on Kafka Streams Processor API
Jorge Quilcate created KAFKA-6938: - Summary: Add documentation for accessing Headers on Kafka Streams Processor API Key: KAFKA-6938 URL: https://issues.apache.org/jira/browse/KAFKA-6938 Project: Kafka Issue Type: Improvement Components: streams Reporter: Jorge Quilcate Assignee: Jorge Quilcate Document changes implemented on KIP-244. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KAFKA-6850) KIP-244: Add Record Header support to Kafka Streams Processor API
Jorge Quilcate created KAFKA-6850: - Summary: KIP-244: Add Record Header support to Kafka Streams Processor API Key: KAFKA-6850 URL: https://issues.apache.org/jira/browse/KAFKA-6850 Project: Kafka Issue Type: Improvement Components: streams Reporter: Jorge Quilcate Assignee: Jorge Quilcate Add support for headers on Streams Processor API. KIP documentation: [https://cwiki.apache.org/confluence/display/KAFKA/KIP-244%3A+Add+Record+Header+support+to+Kafka+Streams+Processor+API] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KAFKA-6395) KIP: Add Record Header support to Kafka Streams
Jorge Quilcate created KAFKA-6395: - Summary: KIP: Add Record Header support to Kafka Streams Key: KAFKA-6395 URL: https://issues.apache.org/jira/browse/KAFKA-6395 Project: Kafka Issue Type: Improvement Components: streams Reporter: Jorge Quilcate Assignee: Jorge Quilcate KIP documentation: https://cwiki.apache.org/confluence/display/KAFKA/KIP-244%3A+Add+Record+Header+support+to+Kafka+Streams -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KAFKA-5520) Extend Consumer Group Reset Offset tool for Stream Applications
Jorge Quilcate created KAFKA-5520: - Summary: Extend Consumer Group Reset Offset tool for Stream Applications Key: KAFKA-5520 URL: https://issues.apache.org/jira/browse/KAFKA-5520 Project: Kafka Issue Type: Improvement Components: core, tools Reporter: Jorge Quilcate Fix For: 0.11.1.0 KIP documentation: TODO -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KAFKA-4743) Add a tool to Reset Consumer Group Offsets
[ https://issues.apache.org/jira/browse/KAFKA-4743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16046071#comment-16046071 ] Jorge Quilcate commented on KAFKA-4743: --- I was about to ask you about the same :) I'd be keen to introduce this for Streams applications. Let me first take a look into `kafka-streams-application-reset` implementation and get back to you to work on the KIP. > Add a tool to Reset Consumer Group Offsets > -- > > Key: KAFKA-4743 > URL: https://issues.apache.org/jira/browse/KAFKA-4743 > Project: Kafka > Issue Type: New Feature > Components: consumer, core, tools >Reporter: Jorge Quilcate >Assignee: Jorge Quilcate > Labels: kip > Fix For: 0.11.0.0 > > > Add an external tool to reset Consumer Group offsets, and achieve rewind over > the topics, without changing client-side code. > https://cwiki.apache.org/confluence/display/KAFKA/KIP-122%3A+Add+Reset+Consumer+Group+Offsets+tooling -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KAFKA-5266) Follow-up improvements for consumer offset reset tool (KIP-122)
[ https://issues.apache.org/jira/browse/KAFKA-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16018581#comment-16018581 ] Jorge Quilcate commented on KAFKA-5266: --- I like 'to-current', I'll implement it. On 4, you're right, NPE is possible in those cases. Wouldn't be better to filter those 'null's and print some warning logs before #toMap? And then catch any other exception on the all #resetOffsets implementation? > Follow-up improvements for consumer offset reset tool (KIP-122) > --- > > Key: KAFKA-5266 > URL: https://issues.apache.org/jira/browse/KAFKA-5266 > Project: Kafka > Issue Type: Bug > Components: tools > Reporter: Jason Gustafson >Assignee: Jorge Quilcate > Fix For: 0.11.0.0 > > > 1. We should try to ensure that offsets are in range for the topic partition. > We currently only verify this for the shift option. > 2. If you provide a CSV file, you shouldn't need to specify one of the > --all-topics or --topic options. > 3. We currently support a "reset to current offsets" option if none of the > supported reset options are provided. This seems kind of useless. Perhaps we > should just enforce that one of the reset options is provided. > 4. The command fails with an NPE if we cannot find one of the offsets we are > trying to reset. It would be better to raise an exception with a friendlier > message. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (KAFKA-5266) Follow-up improvements for consumer offset reset tool (KIP-122)
[ https://issues.apache.org/jira/browse/KAFKA-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16018004#comment-16018004 ] Jorge Quilcate edited comment on KAFKA-5266 at 5/19/17 9:04 PM: [~hachikuji] Thanks! For case 3, maybe `now` could be less verbose but I like `current` also. I'd avoid adding `*-offsets` to the option name because it is kind of implicit from the main `reset-offsets`. But definitely it is better having an explicit option. Any preference between `now` and `current`? For 4, this will be possible only when you set the topic partition manually, right? What if we filter the topicPartitions from allTopics, so if you put some unassigned topic partition you will get an empty list of topicPartitions from #getPartitionsToReset. Check it here: https://github.com/jeqo/kafka/blob/f1a4c5236984de348d4928450c5c0ad5112b6012/core/src/main/scala/kafka/admin/ConsumerGroupCommand.scala#L548 was (Author: jeqo): [~hachikuji] Thanks! For case 3, maybe `--now` could be less verbose but I like `--current` also. I'd avoid adding `*-offsets` to the option name because it is kind of implicit from the main `reset-offsets`. But definitely it is better having an explicit option. Any preference between `--now` and `--current`? For 4, this will be possible only when you set the topic partition manually, right? What if we filter the topicPartitions from allTopics, so if you put some unassigned topic partition you will get an empty list of topicPartitions from #getPartitionsToReset. Check it here: https://github.com/jeqo/kafka/blob/f1a4c5236984de348d4928450c5c0ad5112b6012/core/src/main/scala/kafka/admin/ConsumerGroupCommand.scala#L548 > Follow-up improvements for consumer offset reset tool (KIP-122) > --- > > Key: KAFKA-5266 > URL: https://issues.apache.org/jira/browse/KAFKA-5266 > Project: Kafka > Issue Type: Bug > Components: tools >Reporter: Jason Gustafson >Assignee: Jorge Quilcate > Fix For: 0.11.0.0 > > > 1. We should try to ensure that offsets are in range for the topic partition. > We currently only verify this for the shift option. > 2. If you provide a CSV file, you shouldn't need to specify one of the > --all-topics or --topic options. > 3. We currently support a "reset to current offsets" option if none of the > supported reset options are provided. This seems kind of useless. Perhaps we > should just enforce that one of the reset options is provided. > 4. The command fails with an NPE if we cannot find one of the offsets we are > trying to reset. It would be better to raise an exception with a friendlier > message. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Work started] (KAFKA-5266) Follow-up improvements for consumer offset reset tool (KIP-122)
[ https://issues.apache.org/jira/browse/KAFKA-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5266 started by Jorge Quilcate. - > Follow-up improvements for consumer offset reset tool (KIP-122) > --- > > Key: KAFKA-5266 > URL: https://issues.apache.org/jira/browse/KAFKA-5266 > Project: Kafka > Issue Type: Bug > Components: tools >Reporter: Jason Gustafson > Assignee: Jorge Quilcate > Fix For: 0.11.0.0 > > > 1. We should try to ensure that offsets are in range for the topic partition. > We currently only verify this for the shift option. > 2. If you provide a CSV file, you shouldn't need to specify one of the > --all-topics or --topic options. > 3. We currently support a "reset to current offsets" option if none of the > supported reset options are provided. This seems kind of useless. Perhaps we > should just enforce that one of the reset options is provided. > 4. The command fails with an NPE if we cannot find one of the offsets we are > trying to reset. It would be better to raise an exception with a friendlier > message. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KAFKA-5266) Follow-up improvements for consumer offset reset tool (KIP-122)
[ https://issues.apache.org/jira/browse/KAFKA-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16018004#comment-16018004 ] Jorge Quilcate commented on KAFKA-5266: --- [~hachikuji] Thanks! For case 3, maybe `--now` could be less verbose but I like `--current` also. I'd avoid adding `*-offsets` to the option name because it is kind of implicit from the main `reset-offsets`. But definitely it is better having an explicit option. Any preference between `--now` and `--current`? For 4, this will be possible only when you set the topic partition manually, right? What if we filter the topicPartitions from allTopics, so if you put some unassigned topic partition you will get an empty list of topicPartitions from #getPartitionsToReset. Check it here: https://github.com/jeqo/kafka/blob/f1a4c5236984de348d4928450c5c0ad5112b6012/core/src/main/scala/kafka/admin/ConsumerGroupCommand.scala#L548 > Follow-up improvements for consumer offset reset tool (KIP-122) > --- > > Key: KAFKA-5266 > URL: https://issues.apache.org/jira/browse/KAFKA-5266 > Project: Kafka > Issue Type: Bug > Components: tools >Reporter: Jason Gustafson >Assignee: Jorge Quilcate > Fix For: 0.11.0.0 > > > 1. We should try to ensure that offsets are in range for the topic partition. > We currently only verify this for the shift option. > 2. If you provide a CSV file, you shouldn't need to specify one of the > --all-topics or --topic options. > 3. We currently support a "reset to current offsets" option if none of the > supported reset options are provided. This seems kind of useless. Perhaps we > should just enforce that one of the reset options is provided. > 4. The command fails with an NPE if we cannot find one of the offsets we are > trying to reset. It would be better to raise an exception with a friendlier > message. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KAFKA-5266) Follow-up improvements for consumer offset reset tool (KIP-122)
[ https://issues.apache.org/jira/browse/KAFKA-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017475#comment-16017475 ] Jorge Quilcate commented on KAFKA-5266: --- [~hachikuji] some comments about the improvements: 1. Agree, it will be fixed for the following cases: `resetToOffset`, `resetFromFile` and `resetShiftBy`; as in the other cases, offsets are gathered from the log, not by input. 2. Agree. 3. This option was kept to support the following case: export current offsets, and use it later to go back to an specific point in time. I think this scenario is usable enough to maintain it. 4. This looks OK, but I'm not sure if I get where this could happen. Could you point where this is possible? > Follow-up improvements for consumer offset reset tool (KIP-122) > --- > > Key: KAFKA-5266 > URL: https://issues.apache.org/jira/browse/KAFKA-5266 > Project: Kafka > Issue Type: Bug > Components: tools >Reporter: Jason Gustafson >Assignee: Jorge Quilcate > Fix For: 0.11.0.0 > > > 1. We should try to ensure that offsets are in range for the topic partition. > We currently only verify this for the shift option. > 2. If you provide a CSV file, you shouldn't need to specify one of the > --all-topics or --topic options. > 3. We currently support a "reset to current offsets" option if none of the > supported reset options are provided. This seems kind of useless. Perhaps we > should just enforce that one of the reset options is provided. > 4. The command fails with an NPE if we cannot find one of the offsets we are > trying to reset. It would be better to raise an exception with a friendlier > message. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (KAFKA-5266) Follow-up improvements for consumer offset reset tool (KIP-122)
[ https://issues.apache.org/jira/browse/KAFKA-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Quilcate reassigned KAFKA-5266: - Assignee: Jorge Quilcate > Follow-up improvements for consumer offset reset tool (KIP-122) > --- > > Key: KAFKA-5266 > URL: https://issues.apache.org/jira/browse/KAFKA-5266 > Project: Kafka > Issue Type: Bug > Components: tools >Reporter: Jason Gustafson > Assignee: Jorge Quilcate > Fix For: 0.11.0.0 > > > 1. We should try to ensure that offsets are in range for the topic partition. > We currently only verify this for the shift option. > 2. If you provide a CSV file, you shouldn't need to specify one of the > --all-topics or --topic options. > 3. We currently support a "reset to current offsets" option if none of the > supported reset options are provided. This seems kind of useless. Perhaps we > should just enforce that one of the reset options is provided. > 4. The command fails with an NPE if we cannot find one of the offsets we are > trying to reset. It would be better to raise an exception with a friendlier > message. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KAFKA-4743) Add a tool to Reset Consumer Group Offsets
[ https://issues.apache.org/jira/browse/KAFKA-4743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16003394#comment-16003394 ] Jorge Quilcate commented on KAFKA-4743: --- Hi [~guozhang], I'm using the current operations from Consumer API to seek offsets by position and time, and commit new offsets. Do you have an idea on how this new request protocol could look like and how it will simplify the current implementation? > Add a tool to Reset Consumer Group Offsets > -- > > Key: KAFKA-4743 > URL: https://issues.apache.org/jira/browse/KAFKA-4743 > Project: Kafka > Issue Type: New Feature > Components: consumer, core, tools >Reporter: Jorge Quilcate >Assignee: Jorge Quilcate > Labels: kip > Fix For: 0.11.0.0 > > > Add an external tool to reset Consumer Group offsets, and achieve rewind over > the topics, without changing client-side code. > https://cwiki.apache.org/confluence/display/KAFKA/KIP-122%3A+Add+Reset+Consumer+Group+Offsets+tooling -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KAFKA-4743) Add a tool to Reset Consumer Group Offsets
[ https://issues.apache.org/jira/browse/KAFKA-4743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Quilcate updated KAFKA-4743: -- Description: Add an external tool to reset Consumer Group offsets, and achieve rewind over the topics, without changing client-side code. https://cwiki.apache.org/confluence/display/KAFKA/KIP-122%3A+Add+Reset+Consumer+Group+Offsets+tooling was: Add an external tool to reset Consumer Group offsets, and achieve rewind over the topics, without changing client-side code. https://cwiki.apache.org/confluence/display/KAFKA/KIP-122%3A+Add+a+tool+to+Reset+Consumer+Group+Offsets > Add a tool to Reset Consumer Group Offsets > -- > > Key: KAFKA-4743 > URL: https://issues.apache.org/jira/browse/KAFKA-4743 > Project: Kafka > Issue Type: New Feature > Components: consumer, core, tools > Reporter: Jorge Quilcate > Labels: kip > > Add an external tool to reset Consumer Group offsets, and achieve rewind over > the topics, without changing client-side code. > https://cwiki.apache.org/confluence/display/KAFKA/KIP-122%3A+Add+Reset+Consumer+Group+Offsets+tooling -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KAFKA-4743) Add a tool to Reset Consumer Group Offsets
[ https://issues.apache.org/jira/browse/KAFKA-4743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Quilcate updated KAFKA-4743: -- Description: Add an external tool to reset Consumer Group offsets, and achieve rewind over the topics, without changing client-side code. https://cwiki.apache.org/confluence/display/KAFKA/KIP-122%3A+Add+a+tool+to+Reset+Consumer+Group+Offsets was: Add an external tool to reset Consumer Group offsets, and achieve rewind over the topics, without changing client-side code. This JIRA is related to KIP found here: https://cwiki.apache.org/confluence/display/KAFKA/KIP-122%3A+Add+a+tool+to+Reset+Consumers+Offsets > Add a tool to Reset Consumer Group Offsets > -- > > Key: KAFKA-4743 > URL: https://issues.apache.org/jira/browse/KAFKA-4743 > Project: Kafka > Issue Type: New Feature > Components: consumer, core, tools > Reporter: Jorge Quilcate > Labels: kip > > Add an external tool to reset Consumer Group offsets, and achieve rewind over > the topics, without changing client-side code. > https://cwiki.apache.org/confluence/display/KAFKA/KIP-122%3A+Add+a+tool+to+Reset+Consumer+Group+Offsets -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KAFKA-4743) Add a tool to Reset Consumer Group Offsets
[ https://issues.apache.org/jira/browse/KAFKA-4743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Quilcate updated KAFKA-4743: -- Summary: Add a tool to Reset Consumer Group Offsets (was: Add a tool to Reset Consumers Offsets) > Add a tool to Reset Consumer Group Offsets > -- > > Key: KAFKA-4743 > URL: https://issues.apache.org/jira/browse/KAFKA-4743 > Project: Kafka > Issue Type: New Feature > Components: consumer, core, tools > Reporter: Jorge Quilcate > > Add an external tool to reset Consumer Group offsets, and achieve rewind over > the topics, without changing client-side code. > This JIRA is related to KIP found here: > https://cwiki.apache.org/confluence/display/KAFKA/KIP-122%3A+Add+a+tool+to+Reset+Consumers+Offsets -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (KAFKA-4743) Add a tool to Reset Consumers Offsets
Jorge Quilcate created KAFKA-4743: - Summary: Add a tool to Reset Consumers Offsets Key: KAFKA-4743 URL: https://issues.apache.org/jira/browse/KAFKA-4743 Project: Kafka Issue Type: New Feature Components: consumer, core, tools Reporter: Jorge Quilcate Add an external tool to reset Consumer Group offsets, and achieve rewind over the topics, without changing client-side code. This JIRA is related to KIP found here: https://cwiki.apache.org/confluence/display/KAFKA/KIP-122%3A+Add+a+tool+to+Reset+Consumers+Offsets -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KAFKA-2597) Add Eclipse directories to .gitignore
[
https://issues.apache.org/jira/browse/KAFKA-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15014737#comment-15014737
]
Jorge Quilcate commented on KAFKA-2597:
---
Fixed: https://github.com/apache/kafka/pull/562
> Add Eclipse directories to .gitignore
> -
>
> Key: KAFKA-2597
> URL: https://issues.apache.org/jira/browse/KAFKA-2597
> Project: Kafka
> Issue Type: Improvement
>Reporter: Randall Hauch
>Assignee: Randall Hauch
>Priority: Trivial
> Fix For: 0.9.0.0
>
>
> Add to {{.gitignore}} the Eclipse IDE directories {{.metadata}} and
> {{.recommenders}}. These store state of the IDE's workspace, and should not
> be checked in.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KAFKA-2597) Add Eclipse directories to .gitignore
[
https://issues.apache.org/jira/browse/KAFKA-2597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15014452#comment-15014452
]
Jorge Quilcate commented on KAFKA-2597:
---
'./gradlew eclipse' command is creating 'bin' directories and '.gitignore'
files in each project (clients, connect/file, connect/json, connect/runtime,
core, log4j-appender, streams, and tools) filtering this directory.
Also, when 'gradlew jar' is executed, it generates these files: .cache-main
.cache-tests
If we should filter these files and directories, should we filter in the root
.gitignore or in each project's .gitignore file?
Environment: Eclipse Mars, Scala 2.11, Gradle 2.9, Ubuntu 15.
> Add Eclipse directories to .gitignore
> -
>
> Key: KAFKA-2597
> URL: https://issues.apache.org/jira/browse/KAFKA-2597
> Project: Kafka
> Issue Type: Improvement
>Reporter: Randall Hauch
>Assignee: Randall Hauch
>Priority: Trivial
> Fix For: 0.9.0.0
>
>
> Add to {{.gitignore}} the Eclipse IDE directories {{.metadata}} and
> {{.recommenders}}. These store state of the IDE's workspace, and should not
> be checked in.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
