Note that will not give you the desired range queries of 0 >= x <= 1 and 0
>= y <= 1.
Something akin to Jon's solution could give you those range queries if you
made the x and y components part of the clustering key.
For example, a space of (1,1) could contain all x,y coordinates where x and
y
Generally we still don't consider them stable and you should avoid using
them for the moment. As you can see on my favourite search, the list of
open bugs for MV's is not small, and there are some scary ones in there:
https://issues.apache.org/jira/browse/CASSANDRA-13127?filter=12340733
On 8 May
It gets a little tricky when you try to add in the coordinates to the
clustering key if you want to do operations that are more complex. For
instance, finding all the elements within a radius of point (x,y) isn’t
particularly fun with Cassandra. I recommend moving that logic into the
Hi All,
is static column thread safe or only counter column is thread safe?
Thanks!
Hi,
I'm struggling to understand some problems with respect to materialized
views.
First, I want to understand the example mentioned in
https://issues.apache.org/jira/browse/CASSANDRA-9928 explaining how
multiple non-PK columns in the view PK can lead to unrepairable/orphanized
entries. I
Hm that question is like "My car does not start - whats the problem?".
You have to monitor, monitor, monitor, monitor. I'd strongly advice to
graph as many metrics as you can. Read them from the JMX interface and
write them to a TSDB, visualize them e.g. with Grafana.
Then read logs, trace your
Dear Cassandra Users,
I have some issues since few days with the following cluster:
- 5 nodes
- Cassandra 3.7
- 2 seed nodes
- 1 keyspace with RF=2, 300Go / nodes, WRITE_LEVEL=ONE, READ_LEVEL=ONE
- 1 enormous table (90% of the keyspace)
- TTL for each line insered
The cluster is write
Hi,
> Why did you move from defaults that much?
We were trying to overcome OOM crashes.
> Would you consider giving defaults a try on a canary node and monitor /
compare GC times to other nodes?
We changed settings to default on one node. GC times became about two times
smaller on that node.
>
Hi Lydia,
Yes. This will define the *x*, *y* columns as the components of the
partition key. Note that by doing this both *x* and *y* values will be
required to at a minimum to perform a valid query.
Alternatively, the *x* and *y* values could be combined in into a single
text field as Jon has
