ent:* vendredi 9 juin 2017 10:27
> *To:* Jacques-Henri Berthemet
> *Cc:* user@cassandra.apache.org
> *Subject:* Re: Reg:- Data Modelling For Hierarchy Data
>
>
>
> Hi,
>
> Yes, I am following with single Users table.
>
> Suppose my query patterns are:-
>
> 1)
he.org>
Subject: Reg:- Data Modelling For Hierarchy Data
Hi,
I am working on Music database where we have multiple order of users of our
portal. Different category of users is having some common attributes but some
different attributes based on their registration.
This becomes a hiera
ng as all of them don’t exceed 64k, but you
> could create dedicate columns for all attributes that you know will always
> be there.
>
>
>
> *--*
>
> *Jacques-Henri Berthemet*
>
>
>
> *From:* @Nandan@ [mailto:nandanpriyadarshi...@gmail.com]
> *Sent:* vendredi
exceed 64k, but you could
create dedicate columns for all attributes that you know will always be there.
--
Jacques-Henri Berthemet
From: @Nandan@ [mailto:nandanpriyadarshi...@gmail.com]
Sent: vendredi 9 juin 2017 03:14
To: user@cassandra.apache.org
Subject: Reg:- Data Modelling For Hierarchy Data
Hi,
I am working on Music database where we have multiple order of users of our
portal. Different category of users is having some common attributes but
some different attributes based on their registration.
This becomes a hierarchy pattern. I am attaching one sample hierarchy
pattern of User Modu
