It can be minimum of 20 m to 10 billions
With each entry can contain upto 100 columns
Rajesh
On 19 Feb 2018 9:02 p.m., "Rahul Singh" <rahul.xavier.si...@gmail.com>
wrote:
How much data do you need to store and what is the frequency of reads and
writes.
--
Rahul Singh
rahul.si...@anant.us
Anant Corporation
On Feb 19, 2018, 3:44 AM -0500, Rajesh Kishore <rajesh10si...@gmail.com>,
wrote:
Hi All,
I am a newbie to Cassandra world, got some understanding of the product.
I have a application (which is kind of datastore) for other applications,
the user queries are not fixed i.e the queries can come with any attributes.
In this case, is it recommended to use cassandra ? What benefits we can get
?
Background - The application currently using berkely db for maintaining
entries, we are trying to evaluate if other backend can fit with the
requirement we have.
Now, if we want to use cassandra , I broadly see one table which would
contain all the entries. Now, the question is what should be the correct
partitioning majors ?
entity is
Entry {
id varchar,
objectclasses list<TEXT>
sn
cn
...
...
}
and query can be anything like
a) get all entries based on sn=*
b) get all entries based on sn=A and cn=b
c) get all entries based on sn=A OR objeclass contains person
......
....
Please advise.
Thanks,
Rajesh
