still do ranges, buy you have to do some client side work to work it
> out.
>
> Hope that helps.
>
> -
> Aaron Morton
> Freelance Developer
> @aaronmorton
> http://www.thelastpickle.com
>
> On 24/09/2012, at 5:14 PM, Denis Gabaydulin wrote:
>
>
>
>
> -
> Aaron Morton
> Freelance Developer
> @aaronmorton
> http://www.thelastpickle.com
>
> On 22/09/2012, at 5:07 AM, Denis Gabaydulin wrote:
>
> And some stuff from log:
>
>
> /var/log/cassandra$ cat system.log | grep "Compacting large
B
371.298MB
368.819MB
366.92MB
361.371MB
360.509MB
356.168MB
355.012MB
354.897MB
354.759MB
347.986MB
344.109MB
335.546MB
329.529MB
326.857MB
326.252MB
326.237MB
Is it bad signal?
On Fri, Sep 21, 2012 at 8:22 PM, Denis Gabaydulin wrote:
> Found one more intersting fact.
> As I can see in cfs
Found one more intersting fact.
As I can see in cfstats, compacted row maximum size: 386857368 !
On Fri, Sep 21, 2012 at 12:50 PM, Denis Gabaydulin wrote:
> Reports - is a SuperColumnFamily
>
> Each report has unique identifier (report_id). This is a key of
> SuperColumnFamily.
&g
entire supercolumn in memory whenever
> you read *any* of the subcolumns. This is one of the reasons why composite
> columns are recommended over supercolumns.
>
>
> On Thu, Sep 20, 2012 at 6:45 AM, Denis Gabaydulin wrote:
>>
>> p.s. Cassandra 1.1.4
>>
>&g
p.s. Cassandra 1.1.4
On Thu, Sep 20, 2012 at 3:27 PM, Denis Gabaydulin wrote:
> Hi, all!
>
> We have a cluster with virtual 7 nodes (disk storage is connected to
> nodes with iSCSI). The storage schema is:
>
> Reports:{
> 1:{
> 1:{"value1&qu
Hi, all!
We have a cluster with virtual 7 nodes (disk storage is connected to
nodes with iSCSI). The storage schema is:
Reports:{
1:{
1:{"value1":"some val", "value2":"some val"},
2:{"value1":"some val", "value2":"some val"}
...
},
2:{
1:{"value1":"some
all reports lines of one report will be
>> located on the same node in such configuration?
>
> Yes. If I understood the topology right each replica of a report will
> be stored together on a single node (and even be stored in only a few
> locations on disk if you do not update t
Hi, first of all, let me say thank you for the the amazing product :-)
So, I have a couple of questions about internal physical data layout.
Suppose, I have the following data schema:
Reports:{
1:{
1:{"value1":"some val", "value2":"some val"},
2:{"value1":"some val", "value2":
