ly goal is this bulk retrieval.
>>
>> --
>> *From:* Jack Krupansky <jack.krupan...@gmail.com>
>> *To:* user@cassandra.apache.org
>> *Sent:* Friday, March 11, 2016 7:25 PM
>>
>> *Subject:* Re: Strategy for dividing wide rows be
goal is this bulk retrieval.
>
> --
> *From:* Jack Krupansky <jack.krupan...@gmail.com>
> *To:* user@cassandra.apache.org
> *Sent:* Friday, March 11, 2016 7:25 PM
>
> *Subject:* Re: Strategy for dividing wide rows beyond just adding to the
&g
Krupansky <jack.krupan...@gmail.com>
To: user@cassandra.apache.org
Sent: Friday, March 11, 2016 7:25 PM
Subject: Re: Strategy for dividing wide rows beyond just adding to the
partition key
Thanks, that level of query detail gives us a better picture to focus on. I
think through this som
don't know where to start and end.
Thanks,
Jason
From: Carlos Alonso <i...@mrcalonso.com>
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Sent: Friday, March 11, 2016 7:24 PM
Subject: Re: Strategy for dividing wide rows beyond just adding to the
partition
imeout directly linked to a longer
> seek time in reading through a partition's contents? If that is the case,
> splitting the partition keys into a separate table would be straightforward.
>
> Regards,
>
> Jason
>
> --
> *From:* Jack Krupa
t;>
>> I appreciate your input,
>>
>> Thanks,
>>
>> Jason
>>
>> --
>> *From:* Jack Krupansky <jack.krupan...@gmail.com
>> <javascript:_e(%7B%7D,'cvml','jack.krupan...@gmail.com');>>
>> *To:* "user@cas
he probability of a timeout directly linked to a longer seek
time in reading through a partition's contents? If that is the case, splitting
the partition keys into a separate table would be straightforward.
Regards,
Jason
From: Jack Krupansky <jack.krupan...@gmail.com>
To: user@cassand
TINCT, we get a huge list
> of partition keys for the table because we cannot reduce the scope with a
> where clause.
>
> If there is a recommended pattern that solves this, we haven't come across
> it.
>
> I hope makes the problem clearer.
>
> Thanks,
>
> Jason
>
&g
that solves this, we haven't come across it.
I hope makes the problem clearer.
Thanks,
Jason
From: Jack Krupansky <jack.krupan...@gmail.com>
To: user@cassandra.apache.org; Jason Kania <jason.ka...@ymail.com>
Sent: Thursday, March 10, 2016 10:42 AM
Subject: Re: Strategy for
ail.com>
> *To:* user@cassandra.apache.org; Jason Kania <jason.ka...@ymail.com>
> *Sent:* Thursday, March 10, 2016 10:42 AM
> *Subject:* Re: Strategy for dividing wide rows beyond just adding to the
> partition key
>
> There is an effort underway to support wider rows:
>
ing SELECT DISTINCT pulls all partition
>> keys.
>>
>> Hopefully this is clearer.
>>
>> Again, any suggestions would be appreciated.
>>
>> Thanks,
>>
>> Jason
>>
>> ------
>> *From:* Jonathan Haddad <j
ted.
>
> Thanks,
>
> Jason
>
> --
> *From:* Jonathan Haddad <j...@jonhaddad.com>
> *To:* user@cassandra.apache.org; Jason Kania <jason.ka...@ymail.com>
> *Sent:* Thursday, March 10, 2016 11:21 AM
> *Subject:* Re: Strategy for d
: user@cassandra.apache.org; Jason Kania <jason.ka...@ymail.com>
Sent: Thursday, March 10, 2016 10:42 AM
Subject: Re: Strategy for dividing wide rows beyond just adding to the
partition key
There is an effort underway to support wider
rows:https://issues.apache.org/jira/browse/CASSANDRA-9754
This wo
be appreciated.
Thanks,
Jason
From: Jonathan Haddad <j...@jonhaddad.com>
To: user@cassandra.apache.org; Jason Kania <jason.ka...@ymail.com>
Sent: Thursday, March 10, 2016 11:21 AM
Subject: Re: Strategy for dividing wide rows beyond just adding to the
partition key
Have you consi
Have you considered making the date (or week, or whatever, some time
component) part of your partition key?
something like:
create table sensordata (
sensor_id int,
day date,
ts datetime,
reading int,
primary key((sensor_id, day), ts);
Then if you know you need data by a particular date range,
There is an effort underway to support wider rows:
https://issues.apache.org/jira/browse/CASSANDRA-9754
This won't help you now though. Even with that improvement you still may
need a more optimal data model since large-scale scanning/filtering is
always a very bad idea with Cassandra.
The data
Hi,
We have sensor input that creates very wide rows and operations on these rows
have started to timeout regulary. We have been trying to find a solution to
dividing wide rows but keep hitting limitations that move the problem around
instead of solving it.
We have a partition key consisting of
17 matches
Mail list logo
