Thanks Kurt, that answers my question.
@nandan, id, timestamp ensures unique primary-key.
On Mon, May 21, 2018 at 2:23 PM, kurt greaves wrote:
> Every column will be retrieved (that's populated) from disk and the
> requested column will then be sliced out in memory and sent back.
>
> On 21 M
Every column will be retrieved (that's populated) from disk and the
requested column will then be sliced out in memory and sent back.
On 21 May 2018 at 08:34, sujeet jog wrote:
> Folks,
>
> consider a table with 100 metrics with (id , timestamp ) as key,
> if one wants to do a selective metric r
First question:- [Just as Concern]
How are you making sure that your PK is giving Uniqueness?
For Example:- At the same time, 10 users will write data then how's your
schema going to tackle that.
Now on your question:-
does the read on the specific node happen first bringing all the metric
Folks,
consider a table with 100 metrics with (id , timestamp ) as key,
if one wants to do a selective metric read
select m1 from table where id = 10 and timestamp >= '2017-01-02
:00:00:00'
and timestamp <= '2017-01-02 04:00:00'
does the read on the specific node happen first bringing all the me
