On Sat, Feb 29, 2020 at 8:49 AM Jeff Jirsa wrote:
> If you’re really really advanced you MIGHT be able to use spark +
> cqlsstablewriter to create a ton of sstables with just tombstones one them
> representing deletes, then either nodetool refresh or sstableloader them
> into the cluster
>
> If
Greetings,
In our C* cluster, one node lost time sync and it went to future(16 Mar
2020) for a while.
After fixing timesync, we couldnt update or delete records which were
inserted while node's system time was from the future.
Inspecting sstables, we found that timestamp(TS field value) of these
r
> On Mar 2, 2020, at 2:02 AM, Oleksandr Shulgin
> wrote:
>
>
>> On Sat, Feb 29, 2020 at 8:49 AM Jeff Jirsa wrote:
>
>> If you’re really really advanced you MIGHT be able to use spark +
>> cqlsstablewriter to create a ton of sstables with just tombstones one them
>> representing deletes
You can issue a delete using a future timestamp.
http://cassandra.apache.org/doc/latest/cql/dml.html#grammar-token-update-parameter
Look for USING TIMESTAMP.
Jon
On Mon, Mar 2, 2020, 3:28 AM Furkan Cifci wrote:
> Greetings,
> In our C* cluster, one node lost time sync and it went to future(16
