Hi Brian,
thanks for fixing this so fast!
Ingo
Am 02.02.2013 19:43, schrieb Brian Roach:
Ingo -
As an FYI, once I started looking into this I found you had stumbled
into quite the can of worms. I just finished a pretty comprehensive
set of changes that will now allow proper handling of tombst
Ingo -
As an FYI, once I started looking into this I found you had stumbled
into quite the can of worms. I just finished a pretty comprehensive
set of changes that will now allow proper handling of tombstones in
the Java client - https://github.com/basho/riak-java-client/pull/195
Sorry you had to
Hi Brian,
thanks for the suggestion but I already chose a different solution for
now, if these messages get deleted I just delete the links to the
message and mark the message as "abandoned" and available for reuse. So
I don't run into the conflict if I need to store the message again.
I jus
Ingo -
Unfortunately once you've got a sibling tombstone, things get a bit
tricky. It's not going away until you resolve them which when using
the JSONConverter in the Java client, you can't. Oddly enough, this is
the first time anyone has hit this.
I've got a couple ideas on how to address this
Hi Brian,
thanks for the detailed explaination!
I had a look at an object which constantly fails to load even if retrying:
lftp :~> cat "http://172.22.3.14:8091/riak/m/Um|18498012|4|0|18298081"
Verbinde mit 172.22.3.14 (172.22.3.14) Port 8091
---> GET /riak/m/Um|18498012|4|0|18298081 HTTP/
Ingo -
Riak is returning an object with no contents (which ends up being an
empty String passed to Jackson).
Unless you've somehow mangled the data yourself (which sounds unlikely
given the bit about the 404 from the command line; more on that in a
bit) what's happening is that you're encounterin
Hi Dmitri,
it doesn't happen in my code and it does happen while the riak-client
tries to deserialize a fetched object from riak in a
"fetch-before-store" (see the stack), I also get this error randomly
while trying just to fetch an object from the database.
And if I try to fetch the object
Hi Ingo.
It's difficult to diagnose the exact reason without looking at your code.
But that error is a JSON parser error. It gets thrown whenever the code
tries to parse an empty string as a json object.
The general-case solution is to validate your strings or input streams that
you're turning int
