How to use batch_mutate method in Cassandra Thrift API. I do it below, but
fails:
sc=SuperColumn(1,cs)
cosc=ColumnOrSuperColumn(super_column=sc)
m=Mutation(column_or_supercolumn=cosc)
ml=[]
ml.append(m)
client.batch_mutate(keyspace,{"kw_archive_baidu":list
Thanks!
Column name should be bytes, which is converted from data types which are
defined by CompareWith:
Look at the storage-conf.xml file:
~ BytesType: Simple sort by byte value. No validation is performed.
~ AsciiType: Like BytesType, but validates that the input can be
~
Then what kink of column name should I use?
2010/5/23 Dop Sun
> CompareWith defines type for column name/ super column name, and at the
> moment, key should be always String.
>
>
>
> *From:* huajun qi [mailto:qih...@gmail.com]
> *Sent:* Saturday, May 22, 2010 10:19 PM
> *To:* user@cassandra.apa
I'll try this. HH backs up because nodes are failing. I haven't read the
code, but why should HH suck CPU? As I understand it, there's nothing to
hand off until the destination comes back up, and Gossip should tell us
that, no? In the interim, it's just a cache of writes waiting to be sent.
Is
CompareWith defines type for column name/ super column name, and at the
moment, key should be always String.
From: huajun qi [mailto:qih...@gmail.com]
Sent: Saturday, May 22, 2010 10:19 PM
To: user@cassandra.apache.org
Subject: long type
I set the "CompareWith" property to "longtype", but
The message deserializer has 10m pending tasks before the oom. What do you
think makes the message deserializer blow up? I'd suspect that when it goes
up to 10m pending tasks, don't know how much mem a task actually takes up,
but they may consume a lot of memory. Is there a setting I need to tweak?
I set the "CompareWith" property to "longtype", but I can not insert data.
It seems that something is wrong with the key. If I use longtype comparison,
what key I should use? int?long?
By the way, the language I use is python.
--
Location:
On Sat, May 22, 2010 at 5:59 AM, Steve Lihn wrote:
> This is an indexing question. If I have a structure like
>
> RowKey => { Col => val }
>
> is Col indexed (assuming I will have a lot of columns)?
yes
> On the other hand, if I have a structure like
>
> RowKey => CF => { col => val }
you mean
they are null when there is no compaction in progress
On Fri, May 21, 2010 at 3:13 PM, Anthony Molinaro
wrote:
> On Thu, May 20, 2010 at 02:11:23PM -0700, Jonathan Ellis wrote:
>> No, CM is not exposed to nodetool yet. (You should really be putting
>> metrics into a real monitoring system rather
This is an indexing question. If I have a structure like
RowKey => { Col => val }
is Col indexed (assuming I will have a lot of columns)?
On the other hand, if I have a structure like
RowKey => CF => { col => val }
which components are indexed in addition to RowKey?
Thanks,
Steve
Hi Jonathan,
This sounds a little bit strange, I would expect that NIO server sockets
to be more scalable than regular socket, well I don't have much experience
with tcp programming. What was the scenario you used? The problem I observe
is that most of the requests to Cassandra are quite performa
(a) No
(b) you should restrict it to < 2GB of data in 0.6
On Sat, May 22, 2010 at 3:55 AM, huajun qi wrote:
> Can the value of a column under a super column be a super column?
>
> For examples:
>
> sc={
> name:"name",
> value:{
> {name:"First Name", value:"John"}
>
Done!
Thank you
Pedro Gomes
On May 22, 2010, at 2:07 AM, Jonathan Ellis wrote:
> Thanks!
>
> You should probably add it to http://wiki.apache.org/cassandra/ClientOptions.
>
> On Fri, May 21, 2010 at 12:22 PM, Pedro Gomes
> wrote:
>> Hi all
>> In the following weeks I have developed a plugin
14 matches
Mail list logo
