disk) into JSON, if that is a more
workable format for you.
Sean Durity – Staff Systems Engineer, Cassandra
-Original Message-
From: Marc Richter
Sent: Wednesday, April 22, 2020 6:22 AM
To: user@cassandra.apache.org
Subject: [EXTERNAL] Re: Issues, understanding how CQL works
Hi Jef
>>> need in whatever format you need.
>>>
>>> Or, since this is a single node scenario, you could try sstable2json to
>>> export the
>>> sstables (files on disk) into JSON, if that is a more workable format for
>>> you.
>>>
>
sandra.apache.org
Subject: [EXTERNAL] Re: Issues, understanding how CQL works
Hi Jeff,
thank you for your exhaustive and verbose answer!
Also, a very big "Thank you!" to all the other replyers; I hope you
understand that I summarize all your feedback in this single answer.
From
@cassandra.apache.org
Subject: [EXTERNAL] Re: Issues, understanding how CQL works
Hi Jeff,
thank you for your exhaustive and verbose answer!
Also, a very big "Thank you!" to all the other replyers; I hope you
understand that I summarize all your feedback in this single answer.
From what I under
, if that is a more workable format for
you.
Sean Durity – Staff Systems Engineer, Cassandra
-Original Message-
From: Marc Richter
Sent: Wednesday, April 22, 2020 6:22 AM
To: user@cassandra.apache.org
Subject: [EXTERNAL] Re: Issues, understanding how CQL works
Hi Jeff,
thank you for your
json to
> export the sstables (files on disk) into JSON, if that is a more workable
> format for you.
>
> Sean Durity – Staff Systems Engineer, Cassandra
>
> -Original Message-
> From: Marc Richter
> Sent: Wednesday, April 22, 2020 6:22 AM
> To: user@cassandra.apa
@cassandra.apache.org
Subject: [EXTERNAL] Re: Issues, understanding how CQL works
Hi Jeff,
thank you for your exhaustive and verbose answer!
Also, a very big "Thank you!" to all the other replyers; I hope you
understand that I summarize all your feedback in this single answer.
F
Hi Jeff,
thank you for your exhaustive and verbose answer!
Also, a very big "Thank you!" to all the other replyers; I hope you
understand that I summarize all your feedback in this single answer.
From what I understand from your answers, Cassandra seems to be
optimized to store (and read) dat
Hi Marc,
On Tue, Apr 21, 2020 at 4:20 PM Marc Richter wrote:
> The database is already of round about 260 GB in size.
> I now need to know what is the most recent entry in it; the correct
> column to learn this would be "insertdate".
>
> In SQL I would do something like this:
>
> SELECT insertda
As I learned the hard way (and has already been implied), design your
tables to support your queries.
We have, for example, 9 tables storing the same data, because users wish to
query in different ways. Could be several more tables (if one was being a
purist), but indexes get us the rest of the wa
On Tue, Apr 21, 2020 at 6:20 AM Marc Richter wrote:
> Hi everyone,
>
> I'm very new to Cassandra. I have, however, some experience with SQL.
>
The biggest thing to remember is that Cassandra is designed to scale out to
massive clusters - like thousands of instances. To do that, you can't
assume
To: "user@cassandra.apache.org"
Subject: Re: Issues, understanding how CQL works
Message from External Sender
The short answer is that CQL isn't SQL. It looks a bit like it, but the
structure of the data is totally different. Essentially (ignoring secondary
indexes, which have some
The short answer is that CQL isn't SQL. It looks a bit like it, but the
structure of the data is totally different. Essentially (ignoring
secondary indexes, which have some issues in practice and I think are
generally not recommended) the only way to look the data up is by the
partition key. Any
13 matches
Mail list logo
