reading your description it seems like each data point you get is a self
contained item, is that right? or are you recalculating some data for the
entire block with each new message?
On Sun, Mar 19, 2017 at 9:27 PM, Nate McCall wrote:
> I think you would be better served
Depending on the expected max out of order window, why not order them in
memory? Then you don't need to reread from Cassandra, in case of a problem you
can reread data from Kafka.
-Jesse
> On Dec 21, 2016, at 7:24 PM, Ali Akhtar wrote:
>
> - I'm receiving a batch of
package-the-cassandra-source-code-into-debian-package
>
> 2016-11-02 17:35 GMT+01:00 Jesse Hodges <hodges.je...@gmail.com>:
>
>> Just curious, has anybody created a debian package for this?
>>
>> Thanks, Jesse
>>
>> On Sat, Oct 22, 2016 at 7:45 PM, Ka
Just curious, has anybody created a debian package for this?
Thanks, Jesse
On Sat, Oct 22, 2016 at 7:45 PM, Kai Wang wrote:
> This is awesome! Stability is the king.
>
> Thank you so much!
>
> On Oct 19, 2016 2:56 PM, "Ben Bromhead" wrote:
>
>> Hi All
JIRA, I'm sure it would be greatly appreciated.
>
> https://issues.apache.org/jira/secure/Dashboard.jspa
>
> Jon
>
>
> On Tue, Sep 20, 2016 at 8:10 PM Jesse Hodges <hodges.je...@gmail.com>
> wrote:
>
>> Can you elaborate on why not 3.7?
>>
>> On Tue, Sep 20,
Can you elaborate on why not 3.7?
On Tue, Sep 20, 2016 at 7:41 PM, Jonathan Haddad wrote:
> If you haven't yet deployed to prod I strongly recommend *not* using 3.7.
>
> What network storage are you using? Outside of a handful of highly
> experienced experts using EBS in
> Hey Jesse,
>
> You might wanna check and comment against that issue:
>
> https://issues.apache.org/jira/browse/CASSANDRA-11887
>
> J.
>
> --
> Julien Anguenot (@anguenot)
>
> On Aug 2, 2016, at 3:16 AM, Jesse Hodges <hodges.je...@gmail.com> wrote:
>
Greetings,
I have recently installed ddc/ddc-tools from the deb packages here -
http://debian.datastax.com/datastax-ddc/pool/, but have found that
sstabledump is not included in the packages. I found the following issue
that seems to address it for versions 2.2.7, 3.0.6, 3.6, so I'd think it
Hi, I've got a bit of a conundrum. Recently I upgraded from 2.2.3 to 3.7.0
(ddc distribution). Following the upgrade (though this condition may have
existed prior to upgrade)..
I have a table with a simple partition key and multiple clustering keys,
and I have duplicates of many of the primary