[
https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837764#comment-15837764
]
Mitch Seymour commented on KAFKA-4113:
--
[~guozhang] Yes that is perfect. I haven't had a chance to
[
https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833891#comment-15833891
]
Matthias J. Sax commented on KAFKA-4113:
[~mitch-seymour] see
[
https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15833762#comment-15833762
]
Guozhang Wang commented on KAFKA-4113:
--
Hello [~mitch-seymour], sorry for the late reply. In a recent
[
https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15795304#comment-15795304
]
Mitch Seymour commented on KAFKA-4113:
--
I believe I am experiencing the same issue that [~gfodor]
[
https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15627097#comment-15627097
]
Greg Fodor commented on KAFKA-4113:
---
Hey [~guozhang], I have been able to reproduce a bootstrapping
Great to know! Thanks Greg.
Please keep us posted with any new finding you have.
Guozhang
On Fri, Oct 21, 2016 at 12:35 PM, Greg Fodor wrote:
> I managed to track down one case where we were seeing issues with missing
> data when transitioning to a new node to being a
I managed to track down one case where we were seeing issues with missing
data when transitioning to a new node to being a retention policy on the
topic. There is an additional case but have not been able to repro at this
time. We recently fixed a problem where we were failing to properly
[
https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15593018#comment-15593018
]
Greg Fodor commented on KAFKA-4113:
---
Oh, so it should be doing exactly what makes sense to me -- I am on
[
https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15592931#comment-15592931
]
Guozhang Wang commented on KAFKA-4113:
--
[~gfodor] The main reason we do not log the source KTable is
[
https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15587991#comment-15587991
]
Greg Fodor commented on KAFKA-4113:
---
I guess what I would argue is that KStreamBuilder#table should have
[
https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15587966#comment-15587966
]
Greg Fodor commented on KAFKA-4113:
---
Having played around with Kafka Streams for a while now, I am still
[
https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15468817#comment-15468817
]
Guozhang Wang commented on KAFKA-4113:
--
More thoughts regarding this issue after discussing with
[
https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15458144#comment-15458144
]
Matthias J. Sax commented on KAFKA-4113:
Thanks for pointing out! I read it once. Good post! :)
>
[
https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456866#comment-15456866
]
James Cheng commented on KAFKA-4113:
I wrote a blog post on some other ways to know when you have read
[
https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456332#comment-15456332
]
Matthias J. Sax commented on KAFKA-4113:
Two things to add. (1) prioritizing smaller timestamps in
[
https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15456296#comment-15456296
]
Jay Kreps commented on KAFKA-4113:
--
Don't you get this naturally out of the message timestamps and the
16 matches
Mail list logo