Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for 
change notification.

The following page has been changed by MarkMcBride:
http://wiki.apache.org/cassandra/ThriftInterface

------------------------------------------------------------------------------
    {'name': 'groups', 'columns': [{'columnName': '1', 'value': '1', 
'timestamp': 0}]}]
  }}} 
  
+ == storage configuration impact on the Thrift API ==
+ 
+ Note that some API calls may silently return empty sets if the underlying 
storage configuration doesn't support them.  In particular, get_columns_since 
will only return rows if the column family is ordered by time.
+ 
+ == usage of timestamp in Thrift calls ==
+ 
+ In the examples shown here timestamps are all 0.  This is to make them 
non-clock dependent.  In real world scenarios this is used to provide eventual 
consistency... mutations are ordered by the timestamp supplied by the client.  
In most cases you should set the timestamp to the time at which the data was 
updated, or the current time if that is unavailable.
+ 

Reply via email to