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) combin
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 wrote:
> I would answer your question this way:
>
> 1) Why
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
Jens,
thanks for the response but your reply doesn't serve any purpose. I asked
about use cases suitable for Cassandra. It is a basic question about what
purpose does this technology serve? My use case or requirements do not
matter in that regard. And 'fits our requirements' is not a valid reason
a
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 and
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,
I think you are asking the wrong first question. You should start with "What
are my requirements?". If you are only storing two items that are rarely ever
modified, any database is a good approach. We have no idea what your use case
is. We could speculate about it, but really it all boils
Thanks Manoj. Great post for those who already have Cassandra in production.
However it brings me back to my original post.
All the points you have mentioned apply to any big data technology.
Storage- All of them
Query- All of them. In fact lot of them perform better. Agree that CQL
structure is be
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 wrote:
> Hi,
> I have seen this in a
I've installed ntpd. Thanks!
2014-07-03 23:14 GMT-03:00 Jonathan Haddad :
> 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
> wrote:
> > I have synchronized the clocks and works!
> >
> >
> > 2014-07
Hi Rameez,
If you run a rebuild on an already populated cluster it will simply stream
the data again and you will have a duplicate data set.
What you need to do is stop all the nodes in the new DC and clear out the
data directory. Then comment out num_tokens and populate the initial token
with th
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 H
Does it mean, that Cassandra is not useful for any count queries on more
than one columns?
2014-06-24 15:21 GMT+02:00 Jeremy Jongsma :
> You'd be better off using external indexing (ElasticSearch or Solr),
> Cassandra isn't really designed for this sort of querying.
> On Jun 24, 2014 3:09 AM, "M
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%
d2f980c1-cf82-4659-95ce-ffa3e50ed7
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 o
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
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
It's not reserved but can have a specific meaning in some context.
On Fri, Jul 4, 2014 at 1:29 PM, Philo Yang 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, when I create
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 "timest
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 g
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
wrote:
> Cassandra can handle many more columns (e.g. time series).
> So 100 columns is OK.
>
> Best,
> Romain
>
>
>
> tommaso ba
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 least
Cassandra can handle many more columns (e.g. time series).
So 100 columns is OK.
Best,
Romain
tommaso barbugli a écrit sur 03/07/2014 21:55:18 :
> De : tommaso barbugli
> A : user@cassandra.apache.org,
> Date : 03/07/2014 21:55
> Objet : Re: keyspace with hundreds of columnfamilies
>
> tha
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
24 matches
Mail list logo
