<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 19, 2016, at 3:09 AM, Joel Takvorian <<a href="mailto:jtakvori@redhat.com" class="">jtakvori@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Thanks John, very interesting reading.<div class=""><br class=""></div><div class="">No luck for us in inventory, as there's essentially updates rather than inserts, which is a bit more complicated than the solution described: "<span style="background-color:rgb(245,245,245);color:inherit;font-family:hack;font-size:13px;white-space:pre-line" class="">generally the client needs to be smart enough to merge updates based on a timestamp, with a periodic batch job that cleans out obsolete inserts”</span></div></div></div></blockquote><div><br class=""></div><div>Can you explain more what you mean about there being updates rather than inserts? Inserts and updates are the same in Cassandra. Think of a put operation on a map.</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><span style="background-color:rgb(245,245,245);color:inherit;font-size:13px;white-space:pre-line" class=""><font face="arial, helvetica, sans-serif" class=""><br class=""></font></span></div><div class=""><span style="background-color:rgb(245,245,245);color:inherit;font-size:13px;white-space:pre-line" class=""><font face="arial, helvetica, sans-serif" class="">But now we're considering the alternative of reading/writing the whole graph at once and process queries in memory. If "the whole graph" is too big to fit in memory without problems, then we should find a way to partition it.</font></span></div><div class=""><br class=""></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Sat, Dec 17, 2016 at 2:54 AM, John Sanda <span dir="ltr" class=""><<a href="mailto:jsanda@redhat.com" target="_blank" class="">jsanda@redhat.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="">This thread post <a href="https://goo.gl/8cpSwM" target="_blank" class="">https://goo.gl/8cpSwM</a> <wbr class="">from cassandra-users list has a good write up on an approach for implementing transactions across multiple tables in order to provide stronger consistency. I found it particularly interesting in light of the discussions of inventory and consistency.<span class="HOEnZb"><font color="#888888" class=""><div class=""><br class=""></div><div class="">- John</div></font></span></div><br class="">______________________________<wbr class="">_________________<br class="">
hawkular-dev mailing list<br class="">
<a href="mailto:hawkular-dev@lists.jboss.org" class="">hawkular-dev@lists.jboss.org</a><br class="">
<a href="https://lists.jboss.org/mailman/listinfo/hawkular-dev" rel="noreferrer" target="_blank" class="">https://lists.jboss.org/<wbr class="">mailman/listinfo/hawkular-dev</a><br class="">
<br class=""></blockquote></div><br class=""></div>
_______________________________________________<br class="">hawkular-dev mailing list<br class=""><a href="mailto:hawkular-dev@lists.jboss.org" class="">hawkular-dev@lists.jboss.org</a><br class="">https://lists.jboss.org/mailman/listinfo/hawkular-dev<br class=""></div></blockquote></div><br class=""></body></html>