Hi,
I've just tried to change it to integer and I get exactly the same error.
Thanks,
Davide
On 6 June 2013 23:53, Keith Wright kwri...@nanigans.com wrote:
Could it be because you are writing age as a long but have it defined as an
integer in the table definition?
Davide Anastasia
Hi,
In HotSpot 64-bit, only the server JIT is included.
Cheers
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Cassandra-and-server-JVM-parameter-tp7588196p7588233.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Looking into it further, I believe your issue is that you did not define the
table with compact storage. Without that, CQL3 will treat every column as a
composite (as is hinted in your stack trace where you see AbstractCompositeType
is the cause of the error). Try changing your table
Hi Keith,
You are my hero :-)
It does work now.
Thanks a lot,
Davide
On 7 Jun 2013 10:57, Keith Wright kwri...@nanigans.com wrote:
Looking into it further, I believe your issue is that you did not define
the table with compact storage. Without that, CQL3 will treat every column
as a
I keep having issues with GC. Besides the cluster mentioned above, we also
have a single node development cluster having the same issues. This node
has 12.33 GB data, a couple of million skinny rows and basically no load.
It has default memory settings but keep getting very long stop-the-world GC
Hi
please note that when you drop column family, the data on the disk is not
deleted.
this is something you should do yourself.
Do the files get deleted on GC/server restart?
the question actually translates - do the column family existed after the
restart?
John pls correct me if I am
Conflicts are managed at the column level.
1) If two columns have the same name the column with the highest timestamp
wins.
2) If two columns have the same column name and the same timestamp the
value of the column is compared and the highest* wins.
Someone correct me if I am wrong about the *. I
Like Edward says Cassandra's conflict resolution strategy is LWW (last
write wins). This may seem simplistic, but Cassandra's Big Query-esque data
model makes it less of an issue than in a pure key/value-store like Riak,
for example. When all you have is an opaque value for a key you want to be
Hi,
I am trying to build the storage of stock prices in Cassandra. My queries are
ideally of three types:
- give me everything between time A and time B;
- give me everything about symbol X;
- give me everything of type Y;
...or an intersection of the three. Something I will be happy doing is:
-
We have built a similar system, you can ready about our data model in CQL3
here:
http://www.slideshare.net/carlyeks/nyc-big-tech-day-2013
We are going to be presenting a similar talk next week at the cassandra
summit.
On Fri, Jun 7, 2013 at 12:34 PM, Davide Anastasia
Could this error message be pointing at a proximate cause?
no
If you are talking about 1.2.x then I also have memory problems on the
idle cluster: java memory constantly slow grows up to limit, then spend
long time for GC. I never seen such behaviour for 1.0.x and 1.1.x, where
on idle cluster java memory stay on the same value.
On 06/07/2013 05:19 PM,
On Fri, May 24, 2013 at 10:01 AM, Robert Coli rc...@eventbrite.com wrote:
On Fri, May 24, 2013 at 9:01 AM, Hiller, Dean dean.hil...@nrel.gov wrote:
I seem to remember problems with ghost nodes, etc. and I seem to remember if
you are replacing a node and you don’t use the same ip, this can
I would not mind meeting people there. My cell is 303-517-8902, best to text
me probably or just email me at d...@alvazan.com.
Later,
Dean
I'll be attending and will try and meet up with you :). I see your posts often
on this list -- would love to pick your brain and learn more about what you are
using cassandra for and how it's working for you.
I'm a software engineer at Quantcast and we're just beginning to use cassandra.
So far
I'm currently trying to get Cassandra (1.2.5) and Pig (0.11.1) to play nice
together. I'm running a basic script:
rows = LOAD 'cassandra://keyspace/colfam' USING CassandraStorage();
dump rows;
This fails for my column family which has ~100,000 rows. However, if I
modify the script to this:
Follow-up question: it seems that range queries on the *second* field
of a CompositeType(UUIDType(), UUIDType()) do not work.
If I concatenate the two UUID.hex values into a 32-character string
instead of a CompositeType of two UUIDs, then range queries work
correctly.
This is illustrated
17 matches
Mail list logo
