I don't have grand visions of having fat clients connect directly to
Cassandra to read/write data. Too much risk in my opinion.
On Tue, Oct 25, 2011 at 4:50 PM, Edward Capriolo wrote:
>
> If you do not think restful API's are useful, try to make a fat client that
> speaks a non http or https pro
On Wed, Oct 26, 2011 at 7:35 PM, Ben Gambley wrote:
> Our requirement is to store per user, many unique results (which is
> basically an attempt at some questions ..) so I had thought of having the
> userid as the row key and the result id as columns.
>
> The keys for the result ids are maintaine
Hi,
We plan to put data into different keyspaces, e.g a keyspace specific to
save our own configurations, a keyspace to save data like events, devices
and some other keyspaces to save other type of data. Is there any limitation
on this kind of design. Any pros or cons?
Regards
Boris
On Wed, Oct 26, 2011 at 9:35 PM, Ben Gambley wrote:
>
> Hi Everyone
>
> I have a question with regards read performance and schema design if
> someone could help please.
>
>
> Our requirement is to store per user, many unique results (which is
> basically an attempt at some questions ..) so I had
Hi Everybody,
I have a column family of super-columns with long names. The columns in each
super-column also have long names. I'm using Hector, and what I want to do is
get the last column in each super-column, for a range of super-columns. I was
able to get the last column in a column famil
Hi Everyone
I have a question with regards read performance and schema design if someone
could help please.
Our requirement is to store per user, many unique results (which is basically
an attempt at some questions ..) so I had thought of having the userid as the
row key and the result id as
No Unfortunately I don't have the log files , the system was scratch loaded.
Thanks
Ramesh
Sylvain Lebresne wrote:
>You don't have the full logs of a node leading to the exception by any change ?
>Especially one that leads to a
> java.lang.IllegalArgumentException: Illegal Capacity: -2
>would
You don't have the full logs of a node leading to the exception by any change ?
Especially one that leads to a
java.lang.IllegalArgumentException: Illegal Capacity: -2
would be great.
--
Sylvain
On Wed, Oct 26, 2011 at 6:26 PM, Ramesh Natarajan wrote:
> We are using the final 1.0.0.
>
> Thanks
We are using the final 1.0.0.
Thanks
Ramesh
On Wed, Oct 26, 2011 at 11:16 AM, Sylvain Lebresne wrote:
> Also, to be sure, were you using the 1.0.0 final or some RC when getting this
> exception?
>
> On Fri, Oct 21, 2011 at 8:24 PM, Sylvain Lebresne
> wrote:
>> Would you have the full log for o
Also, to be sure, were you using the 1.0.0 final or some RC when getting this
exception?
On Fri, Oct 21, 2011 at 8:24 PM, Sylvain Lebresne wrote:
> Would you have the full log for one of those node leading to the exception
> that you could share? Not sure that'll help but who knows.
>
> --
> Sylv
On Wed, Oct 26, 2011 at 3:50 PM, Ramesh Natarajan wrote:
> I did some more analysis and I think the compaction for this CF stopped after
> we did a update column family to increase the key cache. Other CF compactions
> were going on without any issues.
> I did another update column family to the
I did some more analysis and I think the compaction for this CF stopped after
we did a update column family to increase the key cache. Other CF compactions
were going on without any issues.
I did another update column family to the same CF with same values as before
and the compaction started ag
Looks like compaction for this column family stopped after some time.
The last message for this column family in the system.log is
INFO [MigrationStage:1] 2011-10-25 16:57:00,385 Migration.java (line
119) Applying migration 43f106c0-ff54-11e0--68877f281daf Update
column family to
org.apache.c
The estimate for the number of keys is computed by summing the key
estimate for each sstable of the CF. For each sstable, the estimate
should be fairly good. However, that's when we sum all the sstable estimates
that we can loose potentially a lot of precision if there is a lot of rows that
have pa
Thanks for the quick response, Jonathan.
My problem was that I've been using a modified conf directory I have saved from
0.8.6
Appreciate the help,Amit
> From: jbel...@gmail.com
> Date: Wed, 26 Oct 2011 01:45:35 -0500
> Subject: Re:
> To: user@cassandra.apache.org
>
> Sounds like you have an ol
15 matches
Mail list logo