Sorry. I have to jump in and disagree. Data is not guaranteed to retire in
scenario 1. Since two nodes do not have data and two nodes may be the only
nodes queried at that CL, the read query may return data or not.
Similarly, in scenario 2, the query may not return the most recent data
because the
Nope. No secondary index. Just a slice query on the PK.
On Tuesday, October 7, 2014, Robert Coli wrote:
> On Tue, Oct 7, 2014 at 3:11 PM, Owen Kim > wrote:
>
>> Sigh, it is a bit grating. I (genuinely) appreciate your acknowledgement
>> of that. Though, I didn't int
since there seems to be a
timing element to it, or at least it's not consistently happening. I
haven't been able to reproduce it on a single node test cluster. I'm moving
on to test a larger one now.
On Tue, Oct 7, 2014 at 2:39 PM, Robert Coli wrote:
> On Tue, Oct 7, 2014 at 2:0
I'm aware. I've had the system up since pre-composite columns and haven't
had the cycles to do a major data and schema migration.
And that's not "slightly" non-responsive.
On Tue, Oct 7, 2014 at 1:49 PM, Robert Coli wrote:
> On Tue, Oct 7, 2014 at 1:38 PM,
Hello,
I'm running Cassandra 1.2.16 with supercolumns and Hector.
create column family CFName
with column_type = 'Super'
and comparator = 'UTF8Type'
and subcomparator = 'UTF8Type'
and default_validation_class = 'UTF8Type'
and key_validation_class = 'UTF8Type'
and read_repair_cha
