cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vincent White (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-14099) LCS ordering of sstables by timestamp is inverted
Date Wed, 13 Dec 2017 04:07:00 GMT


Vincent White updated CASSANDRA-14099:
    Status: Patch Available  (was: Open)

I've created a patch that splits in this comparator in two as a way to maybe help avoid this
confusion in the future. Now that this is split into two I'm not sure if a unit test for ageSortedSSTables
(or the comparators themselves) would be required? I have included a unit test for ageSortedSSTables
on my 3.0.x branch, not sure if it's worth making ageSortedSStable() Public just for this
but I didn't see anywhere else where its behaviour was visible.

[3.0 patch |]
[3.0 utest |]
[3.x patch |]
[trunk patch |]

> LCS ordering of sstables by timestamp is inverted
> -------------------------------------------------
>                 Key: CASSANDRA-14099
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Compaction
>            Reporter: Jeff Jirsa
>            Priority: Minor
>             Fix For: 3.0.x, 3.11.x, 4.x
> In CASSANDRA-14010 we discovered that CASSANDRA-13776 broke sstable ordering by timestamp
(inverted it accidentally). Investigating that revealed that the comparator was expecting
newest-to-oldest for read command, but LCS expects oldest-to-newest.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message