Hi all:
I just enabled full_query_logging_option in my Cassandra.yaml and run nodetool
enablefullquerylog. So far so good.
But when I use fqltool to view the captured binary file using fqltool dump, I
saw that all query statements it captured do not contain the actual value.
They all show u
Thanks Jeff for the information.
On Wed, 10 Nov 2021 at 21:08, Jeff Jirsa wrote:
> This type of delete - which doesnt supply a user_id, so it's deleting a
> range of rows - creates what is known as a range tombstone. It's not tied
> to any given cell, as it covers a range of cells, and supersede
I'm pleased to announce Scylla Rust Driver 0.3.0, an asynchronous CQL
driver for Rust, fully compatible with Apache Cassandra™!
=== Notable changes ===
* Connection management is heavily revamped:
> a configurable pool of connections is kept per node or per shard
(Scylla only)
> shard a
This type of delete - which doesnt supply a user_id, so it's deleting a
range of rows - creates what is known as a range tombstone. It's not tied
to any given cell, as it covers a range of cells, and supersedes/shadows
them when merged (either in the read path or compaction path).
On Wed, Nov 10
HI Team,
I have one table below and want to delete data on this table.
DELETE FROM game.tournament USING TIMESTAMP 161692578000 WHERE
tournament_id = 1 AND version_id = 1 AND partition_id = 1;
Cassandra internally manages the timestamp of each column when some data is
updated on the same
Hi,
Digging in Cassandra logs, I saw this exception happening several times,
see trace below.
I was wondering, what can cause such big messages, and could this error
make a repair session fail? I currently see that my repairs are very long
and sometimes I even stop them cause it seems they are ju
