Folks,
I've been scrounging time to work on a knowledge resource for all things
Cassandra ( Cassandra, DSE, Scylla, YugaByte, Elassandra)
I feel like the Cassandra core community still has the most knowledge even
though people are fragmenting into their brands.
Would love to get your feedback on
Do we have any sustem table which stores all config details which we have
in yaml or cassandra env.sh?
Hi Abdul,
system.local I believe has the info you would want. Here is a link about
querying the system keyspace:
https://docs.datastax.com/en/cql/3.3/cql/cql_using/useQuerySystem.html
Kenneth Brotman
From: Abdul Patel [mailto:abd786...@gmail.com]
Sent: Monday, February 25, 2019 7:2
In 4.0+ you can SELECT * FROM system_views.settings;
Chris
On Mon, Feb 25, 2019 at 9:22 AM Abdul Patel wrote:
> Do we have any sustem table which stores all config details which we have
> in yaml or cassandra env.sh?
Not in any released version, but something similar to that is coming in 4.0
--
Jeff Jirsa
> On Feb 25, 2019, at 7:22 AM, Abdul Patel wrote:
>
> Do we have any sustem table which stores all config details which we have in
> yaml or cassandra env.sh?
--
Thanks!
On Monday, February 25, 2019, Jeff Jirsa wrote:
> Not in any released version, but something similar to that is coming in 4.0
>
> --
> Jeff Jirsa
>
>
> > On Feb 25, 2019, at 7:22 AM, Abdul Patel wrote:
> >
> > Do we have any sustem table which stores all config details which we
> have i
Hi Rahul!
A truly outstanding effort for the community. I think it should be tied to a
complete what’s known as a “Body of Knowledge” which is the best way to
organize it as a learning resource. Otherwise, you are just trying to out
google Google. Lots of luck. They will always have supe
Kenneth,
Thanks for the support! I totally agree and that's exactly how I think of
it.. as a Body of Knowledge. Each of those iterations are to show how
people have asked for the knowledge to be presented so far.
Awesome is a proven format for many people for specific lists of useful
links for a
Hi
Some Cassandra nodes could have rows that are associated with tokens
that aren't owned by those nodes anymore as a result of expansion, this
data will remain until a cleanup compaction is run.
We would like to know the best way to calculate the amount (or close to)
of data that is essenti
A real quick way to get an idea might be to run nodetool status and look at the
imbalance of the data on each node assuming all the nodes have the same specs.
From: Cameron Gandevia [mailto:cameron.gande...@globalrelay.net]
Sent: Monday, February 25, 2019 3:00 PM
To: user@cassandra.apache.org
Wow, this is great! Thanks!
On Mon, Feb 25, 2019 at 7:05 AM Rahul Singh
wrote:
> Folks,
>
> I've been scrounging time to work on a knowledge resource for all things
> Cassandra ( Cassandra, DSE, Scylla, YugaByte, Elassandra)
>
> I feel like the Cassandra core community still has the most knowled
11 matches
Mail list logo
