opened Pull Request #2994 on apache/cassandra
#2994 CASSANDRA-19197-trunk: Fix the correspondingMessagingVersion of SSTable format and improve TTL overflow tests coverage
Mentioned @cassandra
I had a SingleStore database and I decided to switch to Apache Cassandra, transferred all the tables with data, and decided to test the queries. Cassandra doesn't understand "WITH" Clause.
WITH t AS (SELECT * FROM tt), ......
I had a SingleStore database and I decided to switch to Apache Cassandra, transferred all the tables with data, and decided to test the queries. Cassandra doesn't understand "WITH" Clause.
WITH t AS (SELECT * FROM tt), ...
Cassandra does not follow the relational model. Data is modeled on the query. Joins and sub-queries are not supported. Data denormalization and table duplication are required.
From I haven't found anything else about this problem other than this.
I wanted to know what options there are to get out of the situation.
The only idea is to put all the data in one table
commented Pull Request #2983 on apache/cassandra
@Maxwell-Guo are you ok with the PR now? should we move forward to testing?
commented Pull Request #2990 on apache/cassandra
@jacek-lewandowski pointed me the TTL change of behavior is tied to v4 so I retract my previous comment :-)
commented Pull Request #2990 on apache/cassandra
I dropped a comment on removing references to specific versions but other than that let's fire CI imo
commented Pull Request #2990 on apache/cassandra
I would remove all references to C* v4. You don't know how this play out in trunk, future versions and it will be another thing easy to miss
I am trying to migrate from 3.11.6 to 4.1.3 bitnami cassandra
Image: docker.io/bitnami/cassandra:4.1.3
charts :
I am trying to migrate from 3.11.6 to 4.1.3 bitnami cassandra
Image: docker.io/bitnami/cassandra:4.1.3
charts : https://github.com/bitnami/charts/tree/main/bitnami/cassandra
First pod cassandra-0 comes up properly but further pods are not coming up and going to crashloopstate with below errors .
Either getting SStable logs or connection exception to connect to cassandra seeds
describe pod :
-- StackTrace --
java.lang.RuntimeException: No nodes present in the cluster. Has this node finished starting up?
at org.apache.cassandra.dht.Murmur3Partitioner.describeOwnership(Murmur3Partitioner.java:294)
at org.apache.cassandra.service.StorageService.getOwnershipWithPort(StorageService.java:5708)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
Logs :
INFO [MemtableFlushWriter:1] 2023-12-14 08:04:22,542 LogTransaction.java:242 - Unfinished transaction log, deleting /bitnami/cassandra/data/data/system/local-7ad54392bcdd35a684174e047860b377/nb_txn_flush_63dca1a0-9a57-11ee-9303-31245335dc97.log
INFO [main] 2023-12-14 08:04:22,722 MigrationCoordinator.java:257 - Starting migration coordinator and scheduling pulling schema versions every PT1M
INFO [main] 2023-12-14 08:04:23,048 SnapshotManager.java:130 - Scheduling expired snapshot cleanup with initialDelaySeconds=5 and cleanupPeriodSeconds=60
WARN [main] 2023-12-14 08:04:23,542 StorageService.java:1903 - Detected previous bootstrap failure; retrying
INFO [main] 2023-12-14 08:04:23,542 StorageService.java:1893 - JOINING: waiting for ring information
INFO [ScheduledTasks:1] 2023-12-14 08:04:25,461 MessagingMetrics.java:207 - ECHO_REQ messages were dropped in last 5000 ms: 0 internal and 1 cross node. Mean internal dropped latency: 0 ms and Mean cross-node dropped latency: 43388 ms
INFO [ScheduledTasks:1] 2023-12-14 08:04:25,465 StatusLogger.java:65 - Pool Name Active Pending Completed Blocked All Time Blocked
INFO [ScheduledTasks:1] 2023-12-14 08:04:25,465 StatusLogger.java:69 - CompactionExecutor 0 0 0 0 0
INFO [ScheduledTasks:1] 2023-12-14 08:04:25,466 StatusLogger.java:69 - MemtableReclaimMemory 0 0 5 0 0
INFO [ScheduledTasks:1] 2023-12-14 08:04:25,466 StatusLogger.java:69 - GossipStage 0 0 3 0 0
INFO [ScheduledTasks:1] 2023-12-14 08:04:25,466 StatusLogger.java:69 - SecondaryIndexManagement 0 0 1 0 0
INFO [ScheduledTasks:1] 2023-12-14 08:04:25,467 StatusLogger.java:69 - HintsDispatcher 0 0 0 0 0
Cassandra.yaml:
listen_address: 'cassandra-0.cassandra-headless.test.svc.cluster.local' rpc_address: '0.0.0.0' saved_caches_directory: '/bitnami/cassandra/data/saved_caches'
I tried to update cassandra yaml file but its not picking changes as well to add seed configs
commented Pull Request #2990 on apache/cassandra
The new full coverage is nice. Wouldn't you like to preserve the section you removed commented with This code won't run until 2086? I know it does nothing for the test but it helps greatly understand what the test is...
The new full coverage is nice. Wouldn't you like to preserve the section you removed commented with This code won't run until 2086? I know it does nothing for the test but it helps greatly understand what the test is doing. Otherwise it's a loose end and open door for a future reader to be wondering what about that. It's almost like documentation. I would at least add a comment to help a future reader close the circle and connect all the dots. Wdyt?
commented Pull Request #2990 on apache/cassandra
ahh, I haven't looked at the comments, I'll check them now
Mentioned @cassandra
I have a Cassandra table that has a mapping of locations. It has a column with PointType data and another column with location information. Given a latitude and a longitude as input, I want to find the nearest geocordinate present in my table....
I have a Cassandra table that has a mapping of locations. It has a column with PointType data and another column with location information. Given a latitude and a longitude as input, I want to find the nearest geocordinate present in my table. Is it possible through a cql query? Are there any other way around?
I attempted to follow the following documentation: https://docs.datastax.com/en/dse/6.7/cql/cql/cql_using/search_index/queriesGeoSpatial.html
However, I am having difficulty in comprehending it.
commented Pull Request #2977 on apache/cassandra
Using the existing stringifyFileSize seems like the right approach.
opened Pull Request #84 on apache/cassandra-sidecar
#84 CASSANDRASC-88: Allow DriverUtils to be pluggable
opened Pull Request #2993 on apache/cassandra
#2993 Skip version check if an endpoint is dead state
opened Pull Request #2992 on apache/cassandra
#2992 Skip version check if an endpoint is dead state
Mentioned @cassandra
bloom.bg/3Gv3PI3
#opensource pic.twitter.com/V2zGCvuXsH
Mentioned @cassandra
@DataStax @RisingWaveLabs
#cassandra #RisingWave pic.twitter.com/4qnyc1QHxw