yes, you are right, it depend on use cases.
I suggested it is a better choice not only choice. JSON will be better if
any filed change re-write whole data without reading.
I tend to use JSON more, where my data does not change or very rarely, Like
storing demoralized JSON data for analytic purpose.
i would respectfully disagree, what you have said is true but it really
depends on the use case.
1) do you expect to be doing updates to individual fields of an item, or
will you always update all fields at once? if you are doing separate
updates then the first is definitely easier to handle
First is better choice, each filed can be updated separately(write only).
Second you have to take care json yourself (read first-modify-then write).
On Fri, Aug 24, 2012 at 5:45 PM, Roshni Rajagopal <
roshni.rajago...@wal-mart.com> wrote:
> Hi,
>
> Suppose I have a column family to associate a us
Hi,
Suppose I have a column family to associate a user to a dynamic list of items.
I want to store 5-10 key information about the item, & no specific sorting
requirements are there.
I have two options
A) use composite columns
UserId1 : {
: = Betty Crocker,
: = Cake
: = 5
: = Nutella,
: = C
