c and dynamic
> CF.
>
> Hope that helps.
>
> -
> Aaron Morton
> Freelance Developer
> @aaronmorton
> http://www.thelastpickle.com
>
> On 2/10/2012, at 10:37 PM, Cyril Auburtin
> wrote:
>
> > I wanted to know why the highlighted sect
information ?
>>
>> What happens when you read the super column ?
>>
>> Cheers
>>
>> -
>> Aaron Morton
>> Freelance Developer
>> @aaronmorton
>> http://www.thelastpickle.com
>>
>> On 18/09/2012, at 5:33 AM, Cyril Aubur
reelance Developer
>> @aaronmorton
>> http://www.thelastpickle.com
>>
>> On 18/09/2012, at 5:33 AM, Cyril Auburtin
>> wrote:
>>
>> First sorry but I'm using an old version 0.7.10
>>
>> and recently I've come up seeing this
&g
reelance Developer
>> @aaronmorton
>> http://www.thelastpickle.com
>>
>> On 18/09/2012, at 5:33 AM, Cyril Auburtin
>> wrote:
>>
>> First sorry but I'm using an old version 0.7.10
>>
>> and recently I've come up seeing this
&g
no right it's ok, it was a bug on my side
2012/8/11 Tyler Hobbs
>
>
> On Thu, Aug 9, 2012 at 10:43 AM, Cyril Auburtin
> wrote:
>
>> It seems the Thrift method *batch-mutate*, with Mutations, will not
>> update the previous data with the mutation given, but c
Hello
It seems the Thrift method *batch-mutate*, with Mutations, will not update
the previous data with the mutation given, but clear and replace by it?
right?
thanks for answers
How could I do if I have more than one field to update, I should send
several thrft *insert*?
B) become can make repair do more work than
> is needed.
> * Rows wider than in_memory_compaction_limit_in_mb (64) make compaction
> run slower
>
>
> Cheers
>
> -
> Aaron Morton
> Freelance Developer
> @aaronmorton
> http://www.thelastpickle.com
In what extent, having possibly large rows, (many columns (sorted as
timeststamp, or geohash or ...) will be nefast for a muli-node ring.
I guess a row can be read/write just on one node, if yes it's more likely
to fail, (than having one row per timestamp ..)
thanks for explanations
Ok actually in my query call instead of &page=14, I will put
&page=colName141st,
2012/6/12 Sasha Dolgy
> https://github.com/hmsonline/virgil Brian O'Neill posted this a while ago
> ... sits on top of Cassandra to give you the RESTful API you want
>
> Another option ... http://code.google.com/p/r
Verlangen
> I solved this with creating a manual index with as column keys integers
> and column values the uuid's of the results. Then run a slicequery to
> determine the batch to fetch.
>
>
> 2012/6/11 Cyril Auburtin
>
>> using 10 results maximum per page,
>&g
There must be someone or something that triggered nodetool loadbalance or
nodetool move
Le 1 juin 2012 23:18, "Tyler Hobbs" a écrit :
> OpsCenter just periodically calls describe_ring() on different nodes in
> the cluster, so that's how it's getting that information.
>
> Maybe try running nodetoo
query is against rows. Rows keys are hashed (using the Random
> Partitioner) to create tokens, and are stored in token order.
>
> the composites are like chapters between the whole keys set, there must be
> intermediate keys added?
>
> Not sure what you mean.
>
> Cheers
&g
keys set, there must be
intermediate keys added?
2012/5/31 aaron morton
> it is hashed once.
>
> To the partitioner it's just some bytes. Other parts of the code car about
> it's structure.
>
> Cheers
>
> -
> Aaron Morton
> Freelance Developer
> @aaro
gt;
> What is the real advantage compared to super column families?
>
> They are faster.
>
> Cheers
>
> -
> Aaron Morton
> Freelance Developer
> @aaronmorton
> http://www.thelastpickle.com
>
> On 29/05/2012, at 10:08 PM, Cyril Auburtin wro
How is it done in Cassandra to be able to range query on a composite key?
"key1" => (A:A:C), (A:B:C), (A:C:C), (A:D:C), (B,A,C)
like get_range ("key1", start_column=(A,"), end_column=(A, C)); will return
[ (A:B:C), (A:C:C) ] (in pycassa)
I mean does the composite implementation add much overhead
specify the jmx port to nodetool, hard coded in conf/cassandra-env.sh
nodetool -h localhost -p [jmx port] ring
2012/5/27 Douglas Muth
> Hi folks,
>
> I'm a relative newbie to Cassandra, and have been trying to get up to
> speed on it so that I can start using it at $WORK.
>
> I ran into an inte
I update it in cassandra.topology.properties ?
it has this for the 2 cassandra folders:
127.0.0.1=DC1:r1
127.0.0.2=DC1:r1
default=DC1:r1
2012/5/26 Pierre Chalamet
> **
> Your datacenter is 'datacenter1' not 'DC1'.
> - Pierre
> ------
&g
s the cluster actually think
> your node is in DC1?
>
> -Jeremiah
>
> On May 26, 2012, at 6:36 AM, Cyril Auburtin wrote:
>
> I get the same issue on Cassandra 1.1:
>
> create keyspace ks with strategy_class = 'NetworkTopologyStrategy' AND
> strategy_options ={D
Client.executeSet(CliClient.java:896)
at
org.apache.cassandra.cli.CliClient.executeCLIStatement(CliClient.java:213)
at
org.apache.cassandra.cli.CliMain.processStatementInteractive(CliMain.java:219)
at org.apache.cassandra.cli.CliMain.main(CliMain.java:346)
2012/5/26 Cyril Auburtin
> thx, but still
t; All you should need is:
> strategy_options = [{DC1:1}]
>
> On Fri, May 25, 2012 at 1:47 PM, Cyril Auburtin
> wrote:
> > I was using a single node, on cassandra 0.7.10
> >
> > with Network strategy = SimpleStrategy, and replication factor = 1,
> > everything is fine, I
I'm not much advanced in cassandra, but seeing the pycassa doc
http://pycassa.github.com/pycassa/assorted/composite_types.html, for
composites you can't even search for the second term, you need a first
term, the second will filter, you just do range slices on the composite
columns
it's totally di
would match what you're asking for. But since
> your keyspace was created with some capital letters in its name, you just
> need to quote the name in CQL 3:
>
> cqlsh> use "Mykeyspace";
>
> p
>
> On Wed, May 16, 2012 at 3:33 AM, Cyril Auburtin
> wrote:
instance? Maybe you should create a
> Jira ticket.
>
> p
>
>
> On Fri, May 11, 2012 at 2:05 PM, cyril auburtin
> wrote:
>
>> yes it seems so
>>
>> as long as I create (more than just create keyspace mykeyspace) it with
>> cassandra cli, by creati
secondary index you will be loading every row in
>> the database, which with a massive database isn't a good idea. So by
>> requiring at least one EQ on an index, you hopefully limit the set of rows
>> that need to be read into memory to a manageable size. Although obviously
>
the context of a v3
> connection. Maybe someone else can confirm?
>
>
> ------
> *From:* cyril auburtin [mailto:cyril.aubur...@gmail.com]
> *Sent:* Friday, May 11, 2012 11:46 AM
> *To:* user@cassandra.apache.org
> *Subject:* Re: C 1.1 & CQ
it works with a 'raw' keyspace (create keyspace mykeyspace;)
but not with create keyspace mykeyspace with
placement_strategy='SimpleStrategy' and strategy_options =
{replication_factor:1};
( ^ the config mykeyspace had)
2012/5/11 cyril auburtin
> thx just: can't
ion.
>
> Are you using cqlsh? If so, use the "-3" parameter for version 3...
>
>
> --
> *From:* cyril auburtin [mailto:cyril.aubur...@gmail.com]
> *Sent:* Friday, May 11, 2012 10:51 AM
> *To:* user@cassandra.apache.org
> *Subject
I have C* 1.1 but it seems to only come with cql 2.0
INFO 19:35:21,579 Cassandra version: 1.1.0
INFO 19:35:21,581 Thrift API version: 19.30.0
INFO 19:35:21,583 CQL supported versions: 2.0.0,3.0.0-beta1 (default:
2.0.0)
the problem is I would like to create such CF :
CREATE COLUMNFAMILY TaggedP
fully limit the set of rows
> that need to be read into memory to a manageable size. Although obviously
> you can still get into trouble with that as well.
>
>
>
>
> On 05/11/2012 09:39 AM, cyril auburtin wrote:
>
>> Sorry for askign that
>> but Why is it neces
Sorry for askign that
but Why is it necessary to always have at least one EQ comparison
[default@Keyspace1] get test where birth_year>1985;
No indexed columns present in index clause with operator EQ
It oblige to have one dummy indexed column, to do this query
[default@Keyspace1] get test wh
sorry found something interesting here
http://www.datastax.com/download/community
2012/5/10 cyril auburtin
> I wanted to use on Windows, but I don't see the .bat files for cassandra,
> cassandra-cli
> I remember they existed for 0.7.10 I think
>
> thx
>
for that. You can apply it on top of 1.1.
>
> ** **
>
> - Pierre****
>
> ** **
>
> *From:* cyril auburtin [mailto:cyril.aubur...@gmail.com]
> *Sent:* mardi 8 mai 2012 08:56
> *To:* user@cassandra.apache.org
> *Subject:* Re: cassandra1.1 can't start
>
&
05/08, at 1:29, cyril auburtin wrote:
>
> well I uncommented lines96&97 in cassandra-env.sh, with lower values
>
> MAX_HEAP_SIZE="500M"
> HEAP_NEWSIZE="100M"
>
> seems to fix, it
>
> 2012/5/7 cyril auburtin
>
>> The xassandra lauch co
well I uncommented lines96&97 in cassandra-env.sh, with lower values
MAX_HEAP_SIZE="500M"
HEAP_NEWSIZE="100M"
seems to fix, it
2012/5/7 cyril auburtin
> The xassandra lauch command worked the first time
>
> then now I keep getting
>
> INFO 18:18:39,354
The xassandra lauch command worked the first time
then now I keep getting
INFO 18:18:39,354 Starting up server gossip
ERROR 18:18:39,357 Exception in thread Thread[COMMIT-LOG-ALLOCATOR,5,main]
java.io.IOError: java.io.IOException: Map failed
at
org.apache.cassandra.db.commitlog.CommitLogSegment.(
; comment='bla’;
>
> ** **
>
> - Pierre****
>
> ** **
>
> *From:* cyril auburtin [mailto:cyril.aubur...@gmail.com]
> *Sent:* dimanche 6 mai 2012 13:10
> *To:* user@cassandra.apache.org
> *Subject:* [1.1] Can't create column
>
> ** **
>
> [default@ks] create c
[default@ks] create column family Post with column_type = 'Standard' and
column_metadata = [{column_name: 'user', validation_class: 'UTF8Type'},
{column_name: 'type', validation_class: 'UTF8Type'}] and comment = 'bla';
java.lang.RuntimeException:
org.apache.cassandra.db.marshal.MarshalException: ca
rows_cached = 100.0 and keys_cached = 1000.0
and key_cache_save_period = 3600;
2012/5/6 cyril auburtin
> thx
>
> Other question
>
> (I'm moving from cassandra 0.7.10 to 1.1)
>
> the class org.apache.cassandra.thrift.Column.Column 's constructor
> arguments is no
egy=’SimpleStrategy’ and
> strategy_options = [{replication_factor:1}]
>
> ** **
>
> ** **
>
> *From:* cyril auburtin [mailto:cyril.aubur...@gmail.com]
> *Sent:* Sunday, May 06, 2012 10:31 AM
> *To:* user@cassandra.apache.org
> *Subject:* creating keyspace with 1.1
Hello
I have just installed cassandra 1.1
CREATE KEYSPACE Excelsior WITH strategy_class = 'SimpleStrategy' AND
strategy_options:replication_factor = 1;
gives this error:
Syntax error at position 85: mismatched input ':' expecting '='
I've looked in changes but didn't found
Thanks
40 matches
Mail list logo
