Hi Gary,
Thanks for answering my question. I thought that could be a tough
question as Cassandra is quickly evolving recently, but it was great
to know that you guys are always trying to make rolling upgrade
possible for minor upgrades.
My friend is evaluating Cassandra as an HA
Hi
Thanks for the answers,
we are planning to run a cron job that fetches the record and deletes
one by one.
A post which gives more details on this
http://www.mail-archive.com/cassandra-u...@incubator.apache.org/msg02610.html
Regards,
Moses.
On 5/13/10, Joel Pitt joel.p...@gmail.com wrote:
On
We have get_count at the thrift level. You supply a predicate and it
returns the number of columns that match. There is also
multi_get_count, which is the same operation against multiple keys.
Gary.
On Thu, May 13, 2010 at 04:18, Bill de hOra b...@dehora.net wrote:
Admin question - is there
get_count returns the number of columns, not the names of those columns?
I should have been specific, by list the columns, I meant list the
column names.
Bill
Gary Dusbabek wrote:
We have get_count at the thrift level. You supply a predicate and it
returns the number of columns that match.
get_slice
see: http://wiki.apache.org/cassandra/API under get_slice and SlicePredicate
On Thu, May 13, 2010 at 9:45 AM, Bill de hOra b...@dehora.net wrote:
get_count returns the number of columns, not the names of those columns? I
should have been specific, by list the columns, I meant list
In a perfect world there should be (aiming for) a new major Cassandra release
every 2-3 months.
// Roger Schildmeijer
On 13 maj 2010, at 19.43em, Sandeep Kalidindi wrote:
Any idea about how far the 0.7 release is ??
Cheers,
Deepu.
On Thu, May 13, 2010 at 10:52 PM, Vijay
I searched the Wiki and the mailing list archives a bit but couldn't find
the answer.
If I catch an exception from a Cassandra.Client method, in my case
batch_mutate, what's the proper course of action?
Ignoring InvalidRequestException, we have Unavailable, TimedOut, and
generic Thrift
All the Exceptions are documented on the API page
(http://wiki.apache.org/cassandra/API) on the wiki.
* UnavailableException -- Not all the replicas required could be created
and/or read.
* TimedOutException -- The node responsible for the write or read did not
respond during the rpc interval
I suspect the issue in my case is saturation, or that the node has gone
down. In the case of saturation, sleeping and retrying seems to be the
fix. Otherwise setup a new transport/proto/client to a new host in the
cluster. Ok, got it.
Ian
On Thu, May 13, 2010 at 2:20 PM, Roger Schildmeijer
I am not sure this is a good design in Cassandra.
What if I just want to get all the data points for AAPL? Since AAPL is not a
key, how does Cassandra get the data if I don't provide the years?
On Thu, Apr 29, 2010 at 1:09 AM, Schubert Zhang zson...@gmail.com wrote:
key : stock ID, e.g.
I also think that's not a good design, but only because the typical query
would have to hit several column families instead of just one.
To answer your question, use a
http://wiki.apache.org/cassandra/API#KeyRange which
includes AAPL across all years you might want in your
What is changing? A more flexible schema or no need to restart (some kind of
hot-reboot)?
Mongo guys claims that Mongo's advantage is a schema-less design. Basically
you can have any data structure you want and you can change them anyway you
want. This is done in the name of flexibility, but I am
Cassandra has always enforced the tiniest bit of schema. You
basically define how you want your columns and subcolumns to be sorted
within column families. You also name the column families and
keyspaces. That's all though.
The part that is changing is that the keyspaces and column families
Mongo has a rich query API and a weak distribution/replication story.
Cassandra has a narrow (read: weak) query API and a strong
distribution/replication story. If you want really shallow learning
curve, easy querying, etc, won't have that much data, and are handy
with the typical master/slave
On Thu, May 13, 2010 at 12:45 PM, Miguel Verde miguelitov...@gmail.com wrote:
I also think that's not a good design, but only because the typical query
would have to hit several column families instead of just one.
This is completely normal in a columnar store. You query at least one
index
A system called Cages has just been released.
Where needed, you can use Cages to apply locking and soon transactions over
sequences of Cassandra operations.
There is a post explaining how Cages can be used with Cassandra here:
i just figured out that can't do a batch mutate + deletion that uses a
slice range predicate. is adding this functionality targeted for a
particular release? what i am trying to do is delete the first X
columns in a row. i can get around it by requesting all the columns in
question and then
Yes--0.7. I aim to make it part of
https://issues.apache.org/jira/browse/CASSANDRA-494 (remove_slice).
Gary.
On Thu, May 13, 2010 at 16:08, B. Todd Burruss bburr...@real.com wrote:
i just figured out that can't do a batch mutate + deletion that uses a slice
range predicate. is adding this
I agree that it's more normal in a columnar store than in an RDBMS, but in
my experience modelling similar data, the vast majority of the time I want
all of {high, low, close, volume} and optimizing for that would be my goal.
It does seem like Steve has more expansive attributes to track (e.g.
I don't think this is currently possible. There is some work underway to add
it in the future, however:
https://issues.apache.org/jira/browse/CASSANDRA-721
https://issues.apache.org/jira/browse/CASSANDRA-1016
On Thu, May 13, 2010 at 4:04 PM, Beier Cai beier...@gmail.com wrote:
Is it possible
No, but there is ongoing work on it:
* https://issues.apache.org/jira/browse/CASSANDRA-580
* http://www.formspring.me/joestump/q/420668558
* http://permalink.gmane.org/gmane.comp.db.cassandra.user/3740
And in the meantime, an interim patch:
*
thx
On 05/13/2010 02:12 PM, Gary Dusbabek wrote:
Yes--0.7. I aim to make it part of
https://issues.apache.org/jira/browse/CASSANDRA-494 (remove_slice).
Gary.
On Thu, May 13, 2010 at 16:08, B. Todd Burrussbburr...@real.com wrote:
i just figured out that can't do a batch mutate +
Thanks for the info, hopefully it will make it to the next version
Beier, Cai
beier...@gmail.com
On Thu, May 13, 2010 at 2:28 PM, Paul Prescod p...@prescod.net wrote:
No, but there is ongoing work on it:
* https://issues.apache.org/jira/browse/CASSANDRA-580
*
For what I have to handle, yes, there are a lot of attributes (daily) in
addition to the daily prices (OHLC). At securities level, SharesOutstanding,
TradedVolume, ShortInterest. At the company level, even more - MarketCap,
DilutedSharesOutstanding, P/E, P/B, DividendYield, etc, etc.. Seems like
MongoDB encourages you to define your schema in your application code by
using mapping classes. This logically infers that it makes no sense to
define the schema twice, in the database and in your application code.
On Fri, May 14, 2010 at 3:48 AM, Steve Lihn stevel...@gmail.com wrote:
What is
Hi
Is there any auto-purging of keys mechanism (or time to live on key )in
cassandra.
Something, like after so many days, the key and its associated column will be
removed
-Sagar
check out https://issues.apache.org/jira/browse/CASSANDRA-699
-keith
On Thu, May 13, 2010 at 6:46 PM, Sagar Naik sn...@attributor.com wrote:
Hi
Is there any auto-purging of keys mechanism (or time to live on key )in
cassandra.
Something, like after so many days, the key and its associated
Not sure how to comment on this concept. I guess it infers that the database
and application are no longer loosely coupled, but now strongly coupled.
I guess too, that java developers will vote yes, while database architect
and DBA will vote no.
In the traditional sense, enterprise data is the
28 matches
Mail list logo
