If this is write once read many data you may get some benefit from packing all
the info for a product into one column, using something like JSON for the
column value.
>> The one thing that stands out to me with this approach is the number of
>> additonal columns that will be created for a sing
If you want to reduce the number of columns, you could pack all the data
for a product into one column, as in
composite column name-> product_id_1:12.44:1.00:3.00
On 04/12/2012 03:03 PM, Philip Shon wrote:
I am currently working on a data model where the purpose is to look up
multiple produ
I am currently working on a data model where the purpose is to look up
multiple products for given days of the year. Right now, that model
involves the usage of a super column family. e.g.
"2012-04-12": {
"product_id_1": {
price: 12.44,
tax: 1.00,
fees: 3.00,
},
"product_id_2":
