Re: Reg:- Cassandra Data modelling for Search

Hi Michael , MV is also good option when we have to select based on equality search, but here condition is to developing a model for advance partial search way. And Also , In case of MV, suppose we have 2 DC with 3 Nodes on each DC then MV will replicated data based on 6*6 times which will be anoth

NGCC Proposal (Was Re: NGCC?)

## Cassandra list email Hi everybody, Here are current thoughts about structure and timing. Your feedback is welcome. Date: One of 18, 19, or 22 September 2017. We are aware the Tokyo user group is planning an event the first week in October. We’re doing our best to give a buffer there. Venue:

Re: Reg:- Cassandra Data modelling for Search

For queries 1-5 this seems like a potentially good use case for materialized views. Create one table with the videos stored by ID and the materialized views for each of the queries. -- Michael Mior mm...@apache.org 2017-06-11 22:40 GMT-04:00 @Nandan@ : > Hi, > > Currently, I am working on data

Re: Reg:- Cassandra Data modelling for Search

-Virtual tokens are not recommended when using SOLR or cassandra-lucene-index. If you use your table schema you will not have any problem with partition size because your table is *not* a WIDE row table (it does not have clustering keys) The limit for 1 record with those 15 or 20 columns must not

Re: Reg:- Cassandra Data modelling for Search

And due to single table videos, maybe it will go with around 15,20 columns, then we need to also think very carefully about partition sizes also. On Mon, Jun 12, 2017 at 6:33 PM, @Nandan@ wrote: > Yes this is only Option I am also thinking like this as my second options. > Before this I was thin

Re: Reg:- Cassandra Data modelling for Search

Yes this is only Option I am also thinking like this as my second options. Before this I was thinking to do denormalize table based on search columns, but due to partial search this will be not that effective. Now suppose , if we are going with this single table as videos. and implemented with Sol

Re: Reg:- Cassandra Data modelling for Search

Using cassandra collections CREATE TABLE videos ( videoid uuid primary key, title text, actor list, producer list, release_date timestamp, description text, music text, etc... ); When using collection you need to take care of its length. Collections are designed to store

Re: Reg:- Cassandra Data modelling for Search

So In short we have to go with one single table as videos and put primary key as videoid uuid. But then how can we able to handle multiple actor name and producer name. ? On Mon, Jun 12, 2017 at 5:51 PM, Eduardo Alonso wrote: > Yes, you are right. > > Table denormalization is useful just when yo

Re: Reg:- Cassandra Data modelling for Search

Yes, you are right. Table denormalization is useful just when you have unique primary keys, not your case. Denormalized tables are only different in its primary key, every denormalized table contains all the data (it just change how it is structured). So, if you need to index it, do it with just o

Re: Reg:- Cassandra Data modelling for Search

Hi Eduardo, And As we are trying to build an advanced search functionality in which we can able to do partial search based on actor, producer, director, etc. columns. So if we do denormalization of tables then we have to create tables such as below :- video_by_actor video_by_producer video_by_dire

Re: Reg:- Cassandra Data modelling for Search

Hi Edurado, As you mentioned queries 1-6 , In this condition, we have to proceed with a table like as below :- create table videos ( videoid uuid primary key, title text, actor text, producer text, release_date timestamp, description text, music text, etc... ); This table will help to store video

Re: Reg:- Cassandra Data modelling for Search

TLDR shouldBe *PD Eduardo Alonso Vía de las dos Castillas, 33, Ática 4, 3ª Planta 28224 Pozuelo de Alarcón, Madrid Tel: +34 91 828 6473 // www.stratio.com // *@stratiobd * 2017-06-12 10:58 GMT+02:00 Eduardo Alonso : > Hi Nandan: > > So, your system must provide the

Re: Reg:- Cassandra Data modelling for Search

Hi Nandan: So, your system must provide these queries: 1 - SELECT video FROM ... WHERE actor = '...'; 2 - SELECT video FROM ... WHERE producer = '...'; 3 - SELECT video FROM ... WHERE music = '...'; 4 - SELECT video FROM ... WHERE actor = '...' AND producer ='...'; 5 - SELECT video FROM ... WHERE

Re: Reg:- Cassandra Data modelling for Search

I as well think that ES is much better match. With ES you will be able to extends your movie DB much more easily like adding translation,year or other fields. Searching with multiple words , range scan, and more which you will get out of the box . All in all make me as well suggest to use ES.

Re: Reg:- Cassandra Data modelling for Search

But Condition is , I am working with Apache Cassandra Database in which I have to store my data into Cassandra and then have to implement partial search capability. If we need to search based on full search primary key, then it really best and easy to work with Cassandra , but in case of flexible

Re: Reg:- Cassandra Data modelling for Search

I haven't run solr with Cassandra myself. I just meant to run elasticsearch as a completely separate service and write there as well. > On 12 Jun 2017, at 09:45, @Nandan@ wrote: > > Do you mean to use Elastic Search with Cassandra? > Even I am thinking to use Apache Solr With Cassandra. > In

Re: Reg:- Cassandra Data modelling for Search

Do you mean to use Elastic Search with Cassandra? Even I am thinking to use Apache Solr With Cassandra. In that case I have to create distributed tables such as:- 1) video_by_title, video_by_actor, video_by_year etc.. 2) After creating Tables , will have to configure solr core on all tables. Is i

Re: Reg:- Cassandra Data modelling for Search

Why not elasticsearch for this use case? It will make your life much simpler > On 12 Jun 2017, at 04:40, @Nandan@ wrote: > > Hi, > > Currently, I am working on data modeling for Video Company in which we have > different types of users as well as different user functionality. > But currentl