Stop Duplicate Writes in Cassandra with Lightweight Transactions
Use Cassandra lightweight transactions with IF NOT EXISTS and SERIAL consistency to prevent duplicate inserts on a single partition.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Use Cassandra lightweight transactions with IF NOT EXISTS and SERIAL consistency to prevent duplicate inserts on a single partition.
Learn how Cassandra Lightweight Transactions use Paxos to provide linearizable compare-and-set on a single partition, with a concrete UPDATE example, latency numbers, common pitfalls, and verification steps you can run on a 3‑node cluster.
Use CQL and Confluence REST v2 to find pages not updated in a year, flag them with labels, and handle rate limits safely. The post walks through query syntax, body‑format choices, a Python example, and trade‑offs.
Learn how Cassandra Lightweight Transactions provide compare‑and‑set semantics, see a concrete cqlsh example, and understand when their extra latency is worth the guarantee.
Learn how to paginate Confluence’s CQL search endpoint safely: a concrete Bash loop, handling of 429 throttling, sort‑stability concerns, and eventual‑consistency limits.
Cassandra Lightweight Transactions give linearizable compare‑and‑set semantics for unique writes like username reservation, at the cost of higher latency; see how to use, verify, and limit them.
Goal To reliably iterate over thousands of Confluence pages via the REST API while minimizing duplicated or missing items caused by concurrent content changes. Constraints Confluence Cloud v2 uses cursor‑based pagination; Data Center and legacy v1 endpoints use numeric offsets. Offset pagination can skip or duplicate items if pages are added or removed betwe