-It’s probably just a logging / visibility problem, but we should confirm
I think it is.
Cause with tracing on, cqlsh logs that "read 1 live rows... " for the query
with both clustering key restricted but the whole partition (with no clustering
key restriction) has 12 live rows, so i suppo
Done.
https://issues.apache.org/jira/browse/CASSANDRA-15500
Sent using https://www.zoho.com/mail/
On Sun, 12 Jan 2020 19:22:33 +0330 Jeff Jirsa wrote
Can you open a jira so someone can investigate ? It’s probably just a logging /
visibility problem, but we should confirm
Sent
One more better way if you would like to do using cli is
nodetool statusbinary
running: if cql port starts up
Not running: if the machine is not ready to accept reads and writes
On Monday, January 13, 2020, Erick Ramirez wrote:
> Yes, a line like this in the system.log indicates that Cassandra h
Yes, a line like this in the system.log indicates that Cassandra has
started successfully on a node:
INFO [main] 2019-12-17 03:03:37,526 Server.java:156 - Starting listening
> for CQL clients on /x.x.x.x:9042 (unencrypted)...
If you're looking for a simpler way of determining it from the comman
Can you open a jira so someone can investigate ? It’s probably just a logging /
visibility problem, but we should confirm
Sent from my iPhone
> On Jan 12, 2020, at 6:04 AM, onmstester onmstester
> wrote:
>
>
> Using Apache Cassandra 3.11.2, defined a table like this:
>
> create table my_t
Using Apache Cassandra 3.11.2, defined a table like this:
create table my_table(
partition text,
clustering1 int,
clustering2 text,
data set,
primary key (partition, clustering1, clustering2))
and con
