There are a couple of .NET clients listed on the wiki. Aquiles
particularly seems to be getting a lot of attention recently:
http://aquiles.codeplex.com/
Unless you have a specific use case (or are just experimenting) it's
best to avoid raw Thrift and make use of an existing library so you do
not
found the issue, was on the logic of the test
sorry about crying wolf :-p
thanks for reading and all your help guys
Nicolas Santini
On Thu, Dec 16, 2010 at 3:55 PM, Nick Santini wrote:
> btw, inside the test the data row gets deleted, but not the secondary index
> row/columns
>
>
> Nicolas Sa
btw, inside the test the data row gets deleted, but not the secondary index
row/columns
Nicolas Santini
On Thu, Dec 16, 2010 at 3:53 PM, Nick Santini wrote:
> ok, after a few tests and debugs ive found that is actually deleting those
> columns, so great
>
> but the problem is different than w
ok, after a few tests and debugs ive found that is actually deleting those
columns, so great
but the problem is different than what I thought it was. Im running the test
which does:
- create and save a row (here I save the secondary indexes)
- find the row by a secondary index
- delete the row (he
Nick, The docs for the DateTime in .net say it's resolution is only 10ms. You should try to find a higher resolution time source to avoid accidentally sending multiple mutations (including deletions) with the same time stamp. I'm not sure it's the cause of this problem, but it can result in cases w
Im using thrift directly on C#
the code that is trying to delete all the columns referencing the row im
deleting on the secondary index rows looks like this
Mutation mutation = new Mutation();
mutation.Deletion = new Deletion();
mutation.Deletion.Timestamp = DateTime.Now.ToBinary();
List predicat
What client are you using? If you're not using a client, what does your
deletion code look like?
- Tyler
On Wed, Dec 15, 2010 at 4:58 PM, Nick Santini wrote:
> thats not exactly what im seeing, is not a row, but columns on a row that i
> was deleting
>
> ie:
> suppose i have a row where the key
thats not exactly what im seeing, is not a row, but columns on a row that i
was deleting
ie:
suppose i have a row where the key is sec_index_1 where i have two columns
with information about other row keys
sec_index_1 { key1:key1, key2:key2 }
then i add a deletion for the column named key2, run i
There's no problem doing deletions with batch_mutate, but you are probably
seeing this:
http://wiki.apache.org/cassandra/FAQ#range_ghosts
- Tyler
On Wed, Dec 15, 2010 at 4:26 PM, Nick Santini wrote:
> since the 0.7beta2 version doesnt support indexes for Super CF or for
> columns that you might
