On Mon, Jan 14, 2013 at 11:55 PM, aaron morton aa...@thelastpickle.comwrote:
Sylvain,
Out of interest if the select is…
select * from test where interval = 7 and severity = 3 order by id desc
;
Would the the ordering be a no-op or would it still run ?
Yes, as Shahryar said this is
I managed to install apache-cassandra-1.2.0-bin.tar.gz
http://www.apache.org/dyn/closer.cgi?path=/cassandra/1.2.0/apache-cassandra-1.2.0-bin.tar.gz
With java-1.6.0-openjdk-1.6.0.0-1.45.1.11.1.el6.x86_64 I still get the
segmentation fault.
However with
Hi,
Is there any document to follow, in case i migrate cassandra thrift API to
1.2 release? Is it backward compatible with previous releases?
While migrating Kundera to cassandra 1.2, it is complaining on various data
types. Giving weird errors like:
While connecting from cassandra-cli:
I'm currently using Astyanax 1.56.21 to retrieve a entire row. My code:
ColumnListString result = keyspace.prepareQuery(cf_name)
.getKey(key)
.execute().getResult();
But, sometimes Astyanax returns a empty row for a specific key. For
example, on first attempt Astyanax returns a empty row
For those who are using playorm for cassandra, latest release (1.4.4) is
available in maven repo now. It has following new features:
- Support for @NoSqlEmbedable for user defined entities.
- In SJQL, Ability to
- Delete rows(DELETE),
- Delete a single column(DELETECOLUMN),
What is your consistency level set to? If you set it to CL_ONE, you could get
different results or is your database constant and unchanging?
Dean
From: Sávio Teles
savio.te...@lupa.inf.ufg.brmailto:savio.te...@lupa.inf.ufg.br
Reply-To: user@cassandra.apache.orgmailto:user@cassandra.apache.org
I also saw this while testing the
https://github.com/boneill42/naughty-or-nice example project.
--Jimmy
From: Kuldeep Mishra kuld.cs.mis...@gmail.com
Reply-To: user@cassandra.apache.org
Date: Tuesday, January 15, 2013 10:29 AM
To: user@cassandra.apache.org
Subject: error when creating
The statements used to create and populate the data might be mildly useful for
those trying to help - Original Message -From: quot;Kuldeep
Mishraquot; ;kuld.cs.mis...@gmail.com
Hi, we are running a 1.1.6 (datastax) test cluster with 6 nodes. After the
recent 1.2 release we have set up a second cluster - also having 6 nodes
running 1.2 (datastax).
They are now running in parallel. We noticed an increase in the number of
writes in our monitoring tool (Datadog). The tool
I don't think so. Usually you'd use either a Time-UUID or something
like epoch time as the column name to get a range of columns by time
range.
On Tue, Jan 15, 2013 at 10:46 AM, Renato Marroquín Mogrovejo
renatoj.marroq...@gmail.com wrote:
Hi all,
I am having some problems while retrieving
Hi Aaron,
Thanks for answering! Yeah that is what I did but then when looking
into the actual column family created I saw this timestamp column
which Cassandra had created. Are we allowed to use this? What is this
specifically for?
Thanks again for the help!
Renato M.
2013/1/15 Aaron Turner
The timestamp is the time the record was inserted into the Cassandra
node. It's used for conflict resolution, so if two clients insert
different data into the same row/column, Cassandra can pick the
winner (most recent timestamp).
You can set it manually on insert, otherwise the node will pick
Thanks for the explanation Aaron!
Renato M.
2013/1/15 Aaron Turner synfina...@gmail.com:
The timestamp is the time the record was inserted into the Cassandra
node. It's used for conflict resolution, so if two clients insert
different data into the same row/column, Cassandra can pick the
Hello,
Executing a query using an invalid CL with binary protocol leads to an
invalid response streamId (always 0).
I've created following issue then:
https://issues.apache.org/jira/browse/CASSANDRA-5164
Thanks,
- Pierre
I am making heavy use of DataStax OpsCenter to help tune my system and its
great.
And yet puzzling. I see my clients do a burst of Reads causing the
OpsCenter Read Requests chart to go up and stay up until the clients finish
doing their reads. The read request latency chart also goes upbut
I haven't used OpsCenter specifically, so this is a guess: often latency
metrics are based on the last N samples and what is graphed are percentiles
(as opposed to a sliding time window). That means that the graph will
remain the same until more requests occur, as the data that the percentiles
are
16 matches
Mail list logo