I am trying to understand the composite type.
Is this a right way to create a Composite Data ?
<>Follower_For_Users
<>#{"userID",n}:"followerID"
for simplicity I have replaced userID by followerID.
regards,
Ramesh
Please help me understand this.
I am not sure if this is the right place to ask such question.
I read that it is not safe to use Super Column Family.
And the alternative, I found was to use Composite Column Names.
Many managers will have many employees.
*<>Manager_Employee
<>#managerID
<>#emplo
On 01/06/2012 01:48 PM, investtr wrote:
Please help me understand this.
I am not sure if this is the right place to ask such question.
I read that it is not safe to use Super Column Family.
And the alternative, I found was to use Composite Column Names.
Many managers will have many employees
On 01/07/2012 02:38 AM, aaron morton wrote:
Can you provide some context ? e.g. what client are you using ?
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 7/01/2012, at 7:29 AM, investtr wrote:
I am trying to understand the composite
columns with say billion columns is a good performer.
See above, billions of columns may not be a great idea. see
http://thelastpickle.com/2011/07/04/Cassandra-Query-Plans/
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 8/01/2012, at 7:4
We have our development Cassandra 1.0.8 server running on EC2 and wanted
to secure it.
I read securing the entire server with firewall is one of the options.
What are the other cheaper options to secure a development server ?
regards,
Ramesh
On 03/02/2012 08:00 AM, Sasha Dolgy wrote:
Put it on a non-routable internal network.
192.168.x.x
172.16.x.x
Etc...
On Mar 2, 2012 1:56 PM, "investtr" <mailto:investt...@gmail.com>> wrote:
We have our development Cassandra 1.0.8 server running on EC2 and
wanted
