Is there anybody else that might see a problem with just using delete
mutations instead of remove calls?
I'm thinking about changing a Cassandra client to always use delete
mutations when removing objects, that way the "delete/remove" call
interface can be kept the same:
1- the "delete/remove" cli
AFAIK both follow the same path internally.
Aaron
On 12 Apr 2011, at 06:47, Josep Blanquer wrote:
> All,
>
> From a thrift client perspective using Cassandra, there are currently
> 2 options for deleting keys/columns/subcolumns:
>
> 1- One can use the "remove" call: which only takes a column
All,
From a thrift client perspective using Cassandra, there are currently
2 options for deleting keys/columns/subcolumns:
1- One can use the "remove" call: which only takes a column path so
you can only delete 'one thing' at a time (an entire key, an entire
supercolumn, a column or a subcolumn)
