Hello,
is here any update? I can't find any new information.
Thanks.
--
Best Regards,
Jakub Janco
RH - Brno - TPB-C
-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassa
There isn’t, or at least not that I know of.
Some time this year most likely. I don’t think anybody is in a rush for 4.0,
either.
—
AY
On 23 January 2018 at 15:40:36, Jakub Janco (jja...@redhat.com) wrote:
Hello,
is here any update? I can't find any new information.
Thanks.
--
Best
Hi all,
I'm trying to understand the behavior of simple and complex columns in
Cassandra.
I was looking at UnfilteredSerializer.java, serializeRowBody() checks for a
timestamp flag and then only it writes it. In case of writeComplexColumn(),
there is no timestamp being written. Also, as per my
Based on C* 3.x code base, I believe a complex column consists of many
cells and each cell has its own timestamp.
Then, there is a method to compute the maxTimestamp for a complex column:
public long maxTimestamp()
{
long timestamp = complexDeletion.markedForDeleteAt();
for (Cell cell :
I agree. But this method is probably calculating the deletion time to determine
the removal strategy for this complex column.
However, when someone tries to read this complex column and there are multiple
copies of it in more than one sstables, how the read request will determine
which complex d
Preetika,
If I am not missing anything, the Cells.reconcile(Cell c1, Cell c2,
int nowInSec)
method is used for both simple and complex cases to
reconcile cells. It looks like it does take in timestamp into
consideration. In the complex case, the prepared code needs to lay out
the iterators of ce
