This same thing is happening to me, where both $bucket index and my own custom
indexes are returning keys that have been deleted and I can’t remove them.
I am hoping there is a way to fix this as it is causing significant problems
for us in production. It seems to be happening with some frequency
Hi Evan,
Thanks -- that resulted in a list that looks like:
{ok,[<<128,0,0,0>>,
<<128,1,0,0>>,
<<128,2,0,0>>,
<<128,3,0,0>>,
<<128,4,0,0>>,
<<128,5,0,0>>,
... etc ...
That confirms my suspicions that the Java client is mangling the keys
while processing them as unicode s
Since we're talking about indices:
you can attach to the console with `riak attach` (then detach with
control-d (1.3 and below) or control-c (1.4+) note that this is can
kill your node on older versions, so be careful to use the correct
one). Then edit the below to match up with your query, and t
Worth noting here; the current Java client is entirely UTF-8 centric
and is explicitly converting those bytes to UTF-8 strings, so yes ...
that's probably an issue here if I'm understanding things correctly.
Almost everything is copied to/from the protocol buffer message to
Java Strings using the
On 06/11/13 11:30, Evan Vigil-McClanahan wrote:
You can replace int_to_bin with int_to_str to make it easier to debug
in the future, I suppose. I am not sure how to get them to be fetched
as bytes, without may altering the client.
You could just attach to the console and run whatever listing co
You can replace int_to_bin with int_to_str to make it easier to debug
in the future, I suppose. I am not sure how to get them to be fetched
as bytes, without may altering the client.
You could just attach to the console and run whatever listing command
you're running there, which would give you t
Hi Evan,
These keys were originally created by basho-bench, using:
{key_generator, {int_to_bin, {uniform_int, 1}}}.
Of the 10k keys, it seems half could be removed, but not the other half.
Now I've tried storing keys with the same key as the un-deleteable ones,
waiting a minute, and then de
Hi Toby.
It's possible, since they're stored separately, that the objects were
deleted but the indices were left in place because of some error (e.g.
the operation failed for some reason between the object removal and
the index removal). One of the things on the feature list for the
next release
On 01/11/13 14:04, Toby Corkindale wrote:
Hi,
I have around 5000 keys which just won't die.
No matter how many times I delete them, they still show up in the 2i
$bucket=_ index.
Actually attempting to retrieve the keys results in a not-found - even
if I've requested that tombstones be returned.
