Maybe it's because of the "COMPACT STORAGE". Without that, the cells of a CQL3
table definition will be mapped to a composite taking the clustering part of
the key and the column name.
So, i.e. in your case the "value" column should be mapped to a cell with name
column1:value if your def not inc
At those rates, to avoid hot spots, and maintain rows in a manageable size
(~10MB or so), maybe you should partition every 5 or 10 minutes per app_id, so
your partition key looks like i.e 1234_201305081300,
1234_201305081305, 1234_201305081310, 1234_201305081315, etc.
Keep in mind that, when y
t: Re: CqlPreparedResult type info
On Mon, Mar 4, 2013 at 4:13 PM, Adriano Paggi
mailto:adri...@pert.com.ar>> wrote:
Hi, I'm using prepare_cql3_query thrift method, which returns CqlPreparedResult
with type info in variable_types.
The type names returned are partial for collection type
Hi, I'm using prepare_cql3_query thrift method, which returns CqlPreparedResult
with type info in variable_types.
The type names returned are partial for collection types. Returns just MapType
without saying anything about the key-value types. A more intuitive response
could be something like
