Hi,
When I install cassandra on CentOS via yum, I see it also installs openjdk.
Why is that? Given that it is adviced in the documentation to use Oracle
JRE?
See
http://www.datastax.com/documentation/cassandra/2.0/cassandra/install/installRHEL_t.html
?
Also, what is the difference between using
Hi,
I just encountered a bug with 2.1-rc1 (didn't have the chance to update
to rc2 yet), and wondering if it's known or if I should report the issue
on JIRA.
Basically I dropped a cf/table and it failed, then put Cassandra in a
state where neither the table nor the hybrid can be dropped (at
Just so you guys aren't misunderstanding each other; Tommaso, you were not
refering to CQL-style columns, right?
/J
On Fri, Jul 4, 2014 at 10:18 AM, Romain HARDOUIN romain.hardo...@urssaf.fr
wrote:
Cassandra can handle many more columns (e.g. time series).
So 100 columns is OK.
Best,
Hi,
We are running Cassandra 1.2.16 to store data using CQl with the following
structure.
CREATE TABLE sample1 ( row_id text, timeuid timeuuid, value blob, PRIMARY
KEY (row_id, timeuid))
CREATE TABLE sample2 ( row_id text, timeuid timeuuid, value blob, PRIMARY
KEY (row_id, timeuid))
The server
Hi all,
I find in the doc,
http://www.datastax.com/documentation/cql/3.1/cql/cql_reference/keywords_r.html
, keyword timestamp is not reserved. However, when I create a table with
a column named timestamp, it is changed to timestamp which is in double
quotation marks automatically.
Is timestamp
It's not reserved but can have a specific meaning in some context.
On Fri, Jul 4, 2014 at 1:29 PM, Philo Yang ud1...@gmail.com wrote:
Hi all,
I find in the doc,
http://www.datastax.com/documentation/cql/3.1/cql/cql_reference/keywords_r.html
, keyword timestamp is not reserved. However,
hello Team,
I am looking for standard operating procedure to disable vnode in a
production cluster.
This is to enable solr which doesn't work with a cassandra cluster having
vnode enabled.
Any suggestions/
Thanks,
Rameez
Hi Rameez,
I have never done a migration from vnodes to non-vnodes however I would
imagine that the procedure would be the same as its counterpart. As always
testing in dev should be done first.
To move from vnodes to non-vodes I would add a new datacenter to the
cluster with vnodes disabled and
Thanks Mark.
the procedure you shared is useful. I think I have missed the nodetool
rebuild command.
I am trying it out in a non-prod environment.
The num_tokens is set to 1 and initial_token is set to different values
(mine is a 6 node cluster with 3 in each datacenter).
Tried a rolling restart
i did a nodetool rebuild on one of the nodes.
Datacenter: DC1
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
-- Address Load Tokens Owns Host
ID Rack
*UN 10.123.75.51 10.54 GB 256 16.0%
Hi,
I have seen this in a lot of replies that Cassandra is not designed for
this and that. I don't want to sound rude, i just need some info about this
so that i can compare it to technologies like hbase, mongo,
elasticsearch, solr,
etc.
1) what is Cassandra designed for. Heave writes yes. So is
I've installed ntpd. Thanks!
2014-07-03 23:14 GMT-03:00 Jonathan Haddad j...@jonhaddad.com:
Make sure you've got ntpd running, otherwise this will be an ongoing
nightmare.
On Thu, Jul 3, 2014 at 5:00 PM, Sávio S. Teles de Oliveira
savio.te...@cuia.com.br wrote:
I have synchronized the
These are my personal opinions based on few months using Cassandra. These
are my views. Others
may have different opinion
http://khangaonkar.blogspot.com/2014/06/apache-cassandra-things-to-consider.html
regards
On Fri, Jul 4, 2014 at 7:37 AM, Prem Yadav ipremya...@gmail.com wrote:
Hi,
I
I’ve supported a variety of different “big data” systems and most have their
own particular set of use cases that make sense. Having said that, I believe
that Cassandra uniquely excels at the following:
* Low write latency with respect to small to medium write sizes (logs, sensor
data, etc.)
*
Hi Mike,
To learn get subsecond performance on your queries using _any_ database you
need to use proper indexing. Like Jeremy said, Solr will do this.
If you'd like to try to solve this using Cassandra you need to learn the
difference between partition and clustering in your primary key
I would answer your question this way:
1) Why should I choose C* ?
a. linear scalability, throughputs scale almost linearly with number of
nodes
b. almost unbounded extensivity (there is no limit, or at least huge
limit in term of number of nodes you can have on a cluster)
c. operational
Duy,
if you are not already working for Datastax, they should hire you. :)
Great response. You have given me some good points to think about. I will
do the rest of the research.
Thanks.
On Fri, Jul 4, 2014 at 10:10 PM, DuyHai Doan doanduy...@gmail.com wrote:
I would answer your question
Elasticsearch and Solr are “search platforms”, not “databases”. The best
description for Cassandra, especially for a CTO, is its home page:
http://cassandra.apache.org/
Even if you have seen it before, please read it again. There is a lot packed
into a few words.
DataStax Enterprise (DSE)
18 matches
Mail list logo