Very useful.. thank you!
Hi Tim,
>
> Not sure if you've seen this, but I'd start from DataStax's documentation:
>
>
> http://www.datastax.com/documentation/cassandra/2.0/webhelp/index.html#cassandra/architecture/architecturePlanningAbout_c.html?pagename=docs&version=1.2&file=cluster_architecture/
Yes. Sorry. It was me being a fool. I didn't update the rackdc.properties
file on the new version
From: Robert Coli [mailto:rc...@eventbrite.com]
Sent: 24 September 2013 01:52
To: user@cassandra.apache.org
Subject: Re: cass 1.2.8 -> 1.2.9
On Wed, Sep 11, 2013 at 7:42 AM, Christopher Wirt
Hi Sylvain,
I was not describing the problem correctly. I'm sorry for this. This is the
situation:
1. I'm populating the DB with the java-driver (INSERT INTO...). Some fields
that are part of the primary key is *empty strings*. This works fine.
2. I'm trying to populate the DB from a CSV (COPY ..
On Mon, 23 Sep 2013 21:39:50 +
Stephanie Jackson wrote:
> How can I figure out why there's such a huge difference in results on
> one node and not on the other?
Tiny question - are you running two (or more) nodes on the same
physical machine, by using different bind IP addresses? I'm running
Oh. That would be a COPY thing then. I'm not extremely familiar with cqlsh
code (which COPY is part of) but looking at the online help for it, it
seems to have a 'NULL' option that allows to define which character is used
to represent nulls. And by default, it does is an empty string. So you
could
Hi,
We are facing problem while exporting data from Cassandra to MySql database.
For example,
1. I have created keyspace called test_ks and column family called test_cf in
cassandra using cql.
I have inserted some dummy data into test_cf and corresponding files are
created in the folder /var/li
On Sep 24, 2013, at 5:05 AM, 谢良 wrote:
> it looks to me that "MaxTenuringThreshold" is too small, do you have any
> chance to try with a bigger one, like 4 or 8 or sth else?
MaxTenuringThreshold=1 seems a bit odd, yes. But it is the Cassandra default,
maybe there is a reason for this? Perhaps
On Sep 24, 2013, at 5:18 AM, Mohit Anchlia wrote:
> Your ParNew size is way too small. Generally 4GB ParNew (-Xmn) works out best
> for 16GB heap
I was afraid that a 4GB ParNew would cause Young GCs to take too long. I'm
going to test higher ParNew values.
Thanks,
André
signature.asc
Descri
Many applications in thrift use the wide row with composite column name and as
an example, let's say golf score for instance and we end up with golf score :
pk like so
null : pk56
null : pk45
89 : pk90
89: pk87
90: pk101
95: pk17
Notice that there are some who do not have a golf score(zero woul
Short answer: not, this is not correct.
Longer answer: what you call "null" is actually an empty value (which is
*not* the same thing, unless you consider an empty string is the same thing
than a null string). As it happens, C* always an empty value as a valid
value for any type and that's true of
Tested on WINDOWS : On startup of the 2.0.0 version from 1.2.x files I get an
error as listed below.
This is due to the code in LeveledManifest:: mutateLevel. The method already
has a comment saying that it is scary ...
On windows, one cannot use the File::rename if the target file name already
What version of 1.2.x?
Unfortunately, you must go through 1.2.9 first. See
https://github.com/apache/cassandra/blob/cassandra-2.0.0/NEWS.txt#L19-L24
On Tue, Sep 24, 2013 at 8:57 AM, Desimpel, Ignace <
ignace.desim...@nuance.com> wrote:
> Tested on WINDOWS : On startup of the 2.0.0 version from
Thanks Sylvain,
However,we tried missing the value but it didn't work :(
So our code is like below where we are using 3 values if colname is not
null..else 2 values..
if (key != null) {
PreparedStatement statement = session.prepare("INSERT INTO
keys.StringIndice (id,
> However,we tried missing the value but it didn't work :(
>
Right, because not providing a value is akin to having a null value (in the
CQL3 sense of the term, which is different from what Dean asked about) and
null values are not allowed for primary key columns.
You could however insert an *empt
This is on Cassandra 1.2.9 though packaged into DSE which I suspect may
come into play here. I didn't really get to the bottom of it other than to
up the queue to 32 which is about the number of CFs I have. After that,
mutation drops disappeared and the FlushWriter blocks went away.
On Mon, Sep
Ok. Great. It works for String and Decimal/Float but not for integer data
type..
i.e,, if I am passing "" to the composite key column which is either text
or float, it works..
session.execute(boundStatement.bind(rowkey, "", ByteBuffer.wrap(value)));
But not working with bigint, int or varint..and
On Tue, Sep 24, 2013 at 6:17 PM, Vikas Goyal wrote:
> Ok. Great. It works for String and Decimal/Float but not for integer data
> type..
> i.e,, if I am passing "" to the composite key column which is either text
> or float, it works..
>
> session.execute(boundStatement.bind(rowkey, "", ByteBuffe
Java has Integer as opposed to int which is what I represent "golf scores" with
so to speak in my example. In this case, Integer can be null but of course
maps to "empty" just fine. What about querying for all golf scores that are
"empty" then?
Ie. This sounds like this solution would be perf
On Sun, Sep 8, 2013 at 4:00 AM, Andrew Cobley wrote:
> reduce_cache_sizes_at: 0
> reduce_cache_capacity_to: 0
>
...
> I'm assuming the blog must be talking about C* prior to version 2.0
> because these settings do not appear in 2.0's .yaml file.
>
...
> Why where they removed and what's the a
Let's say I've initialized a *SSTableSimpleWriter* instance and a new
column with TTL set :
*SSTableSimpleWriter writer = new SSTableSimpleWriter( ... /* params here
*/);*
*Column column;*
What is the difference between calling *writer.addColumn()* on the column's
name and value, and *writer.addE
Hello folks,
What is the best version to upgrade from C* 1.1.10 to 1.2.X? Any
suggestions?
Thanks,
Paulo
On Tue, Sep 24, 2013 at 1:17 PM, Paulo Motta wrote:
> What is the best version to upgrade from C* 1.1.10 to 1.2.X? Any
> suggestions?
>
Not sure what you're asking, but go to at-least-1.2.9. Current is 1.2.10,
so use that.
=Rob
Doesn't the probability of something going wrong increases as the gap
between the versions increase? So, using this reasoning, upgrading from
1.1.10 to 1.2.6 would have less chance of something going wrong then from
1.1.10 to 1.2.9 or 1.2.10.
I'm hoping this reasoning is wrong and I can update dir
On Tue, Sep 24, 2013 at 1:41 PM, Paulo Motta wrote:
> Doesn't the probability of something going wrong increases as the gap
> between the versions increase? So, using this reasoning, upgrading from
> 1.1.10 to 1.2.6 would have less chance of something going wrong then from
> 1.1.10 to 1.2.9 or 1.2
Cool, sounds fair enough. Thanks for the help, Rob!
If anyone has upgraded from 1.1.X to 1.2.X, please feel invited to share
any tips on issues you're encountered that are not yet documented.
Cheers,
Paulo
2013/9/24 Robert Coli
> On Tue, Sep 24, 2013 at 1:41 PM, Paulo Motta wrote:
>
>> Doesn
On Tue, Sep 24, 2013 at 2:33 PM, Paulo Motta wrote:
> If anyone has upgraded from 1.1.X to 1.2.X, please feel invited to share
> any tips on issues you're encountered that are not yet documented.
>
Exceptions like the below relate to the change in hinted handoff format and
can be safely ignored a
As an update to this thread, we conducted several tests with
Cassandra-1.2.9, varying parameters such as partitioner
(Murmur3Partitioner/RandomParttioner), using NetworkToplogyStrategy (with
Ec2Snitch) / SimpleStrategy (with SimpleSnitch) across 2 Availability zones
and 1 AZ. We also tested the con
Hi Paulo,
I just completed a migration from 1.1.10 to 1.2.10 and it was surprisingly
painless.
The course of action that I took:
1) describe cluster - make sure all nodes are on the same schema
2) shutoff all maintenance tasks; i.e. make sure no scheduled repair is
going to kick off in the middle
Hi,
Just had a go at upgrading a node to the latest stable c* 2 release and
think I ran into some issues with manifest migration.
On initial start up I hit this error as it starts to load the first of my
CF.
INFO [main] 2013-09-24 22:56:01,018 LegacyLeveledManifest.java (line 89)
Migra
29 matches
Mail list logo
