<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Dec 15, 2016 at 2:53 PM, Emmanuel Bernard <span dir="ltr"><<a href="mailto:emmanuel@hibernate.org" target="_blank">emmanuel@hibernate.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;"><span class="gmail-"><br><div><blockquote type="cite"><div>On 15 Dec 2016, at 11:18, Gustavo Fernandes <<a href="mailto:gustavo@infinispan.org" target="_blank">gustavo@infinispan.org</a>> wrote:</div><br class="gmail-m_-119706947963337183Apple-interchange-newline"><div><div dir="ltr" style="font-family:helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">On Thu, Dec 15, 2016 at 9:54 AM, Emmanuel Bernard<span class="gmail-m_-119706947963337183Apple-converted-space"> </span><span dir="ltr"><<a href="mailto:emmanuel@hibernate.org" target="_blank">emmanuel@hibernate.<wbr>org</a>></span><span class="gmail-m_-119706947963337183Apple-converted-space"> </span>wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">The goal is as followed: allow to collect all changes to push them to Debezium and thus Kafka.<br><br>This need does not require to remember all changes since the beginning of time in Infinispan. Just enough to:<br>- let Kafka catchup assuming it is the bottleneck<br>- let us not lose a change in Kafka when it happened in Infinispan (coordinator, owner, replicas dying)<br><br>The ability to read back history would then be handled by the Debezium / Kafka tail, not infinispan itself.<br><br></blockquote><div><br></div><div>Having an embedded Debezium connector pushing everything to Kafka sounds cool, but what impact would it bring to the other stream consumers:<br><br>* Remote listeners, which is supported in several clients apart from Java<br></div><div>* Continuous Queries (the same)<br></div><div>* Spark Stream<br></div><div>* Other eventual 3rd party stream processors: Apache Flick, Storm, etc.<br><br></div><div> </div></div></div></div></div></blockquote><br></div></span><div>Impact as in perf impact? Potential redesign impact? Or are you thinking of another question?</div></div></blockquote><div><br><br></div><div>You mentioned that "<span class="gmail-">The ability to read back history would then be handled by the Debezium / Kafka tail, not infinispan itself", my question<br></span></div><div><span class="gmail-">was how the other consumers would get access to that history.<br></span></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>______________________________<wbr>_________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/infinispan-<wbr>dev</a><br></blockquote></div><br></div></div>