Thanks Guozhang 🙏
upgrading kafka stream version to 1.1.0 fixed the issue 👍
On Sat, Sep 1, 2018 at 10:39 PM Guozhang Wang wrote:
> Hello Amir,
>
> The issue you described seems like an old bug that is resolved since 1.1.0
> (as part of the fix in https://jira.apache.org/jira/browse/KAFKA-6150).
Hello Amir,
The issue you described seems like an old bug that is resolved since 1.1.0
(as part of the fix in https://jira.apache.org/jira/browse/KAFKA-6150).
Could you try out that version?
You do not need to upgrade broker in order to use newer Streams library
versions.
Guozhang
On Sat, Sep 1
Oh thank you for pointing that out, in the screenshot i sent i indeed
forgot that parameter.
It was an attempt to reproduce an error encountered on another system
On that system i can see that the source code includes the --execute
command.
I will send you logs, screenshots etc. using the original
Hello
Did you add --execute to the command?
Which command did you use?
Best regards
Patrik
> Am 01.09.2018 um 14:54 schrieb Joseph M'BIMBI-BENE :
>
> Hello everyone,
>
> Hopefully this is the appropriate mailing list for my message.
> When i am trying to reset the offset of some consumer group,
Hello everyone,
Hopefully this is the appropriate mailing list for my message.
When i am trying to reset the offset of some consumer group, i get some
echo telling me that the offset has indeed been reset to earliest or
latest, but checking right after, the offset is still at its previous
position
Hi Guys!
I use kafka streams reduce function and it creates some state store change
log kafka internal topic ( like
app-KSTREAM-REDUCE-STATE-STORE-02-changelog ).
I wanted to set *retention bytes* and change *cleanup policy* to *delete*
to prevent the storage being full. I set following
