I heard it's not a good practice to enable vnode if using cassandra lucene index. Is it still true? I'm using apache cassandra 3.0.5 and matching stratio lucene indexer.
Thanks.
According to the docs it is still true.
Related
Can anyone tell if we are creating SASI index then it will create index on node level or cluster level. How SASI different with normal Secondary Index? Is it worth to use or not?
However, I went through the documentation but did understand much about pros and cons.
When I studied the document found "SSTable attached secondary indexes (SASI) can be created on a non-collection column defined in a table" so it should be distibuted across the cluster.
I understand that Cassandra is a NoSQL db and patching it with many indices is not the way to go, but here I'm looking at solution for my analytics cluster, not for the production/real-time one.
So I think it makes sense to add indices to reduce the amount of data filtered by Spark.
How do native Cassandra secondary indices compare to Lucene's indices?
Many functionalities are not available with Cassandra alone, but what about things that you can do with both?
Is it better / does it make sense to only use Lucene?
Another advantage that I see is that I can install Lucene only on my analytics cluster, without overloading the real-time one with indices (and therefore improving the write performance on that side).
Don't bother with Lucene integration
Since Cassandra 3.4, we have a new secondary index called SASI that offers full text search and is quite performant.
Read this: https://github.com/apache/cassandra/blob/trunk/doc/SASI.md
I have just started reading about datastax cassandra few days back so I am sort of newbie in this technology. I have some doubts/queries and need to get clarification. Such as:
Which version of Cassandra is more suitable to use 2.1/2.0 ? Right now I am using 2.1 which is not stable and recommended to use. Even though using this(2.1) leads to some problems in future then what would be the better choice to opt for ?
Does Cassandra supports "Like" clause ? If yes, in which version ? And how ? If not, then what can be the alternative?
I'm using apache cassandra 2.1.2. It's been running in prod since release. No major issues.
No... look to pair it up with Lucene or elasticsearch. If you're on DSE, DSE search nodes can give you this feature. You might even want to check out http://www.openstratio.org/blog/advanced-search-in-cassandra/ . The guys at stratio have added the ability to have a text column representing a lucene query, which is quite interesting.
In SQL, we have an option to specify the LIKE operator in the where clause. Is there something like that in Cassandra? I am building a search feature for my site. All the data resides on Cassandra. So, it would be easier to search for keywords with LIKE operator.
No.You dont have such feature in cassandra. You gotto create a search engine on the data that is stored in cassandra to index the entries in cassandra may be. Cassandra serves as a container to hold your data and does not provide such features like full text search yet(I doubt if they will really as the storage is across SSTables).
If you need search capabilities on cassandra data, look no further than DSE:
http://docs.datastax.com/en/datastax_enterprise/4.7/datastax_enterprise/srch/srchIntro.html
Is there any way to use Apache Lucene and have it store values and retrieve values from a Cassandra cluster?
The hard way: implement a custom index type on top of Lucene and teach Cassandra to query it. There is also a two year old ticket open for this that you could watch.
The expensive way: buy a DataStax Enterprise license.
You should try out https://code.google.com/p/lucene-on-cassandra/ . Takes a different approach to the DataStax approach.