Also, a property annotated with a Riak annotation was kept in the Json
only if it has been explicitly annotated with @JsonProperty or has not
been annotated with a Riak property.
This was accomplished with the following code from the old client:
static {
RIAK_ANNOTATIONS.add(RiakK
Hi,
I see now there is support for 2i which we needed in order to migrate to
2.x, there was another issue with the old client which forced us to
modify the client, such issue was related to the following, let me put
an example:
public class POJO {
@RiakKey
public String getKey() {
/
Hi Guido,
I see that you opened up this PR, thanks -
https://github.com/basho/riak-java-client/pull/631
Would you mind filing these questions in an issue on GitHub to
continue the discussion there?
https://github.com/basho/riak-java-client/issues/new
Thanks!
--
Luke Bakken
Engineer
lbak...@bas
Hi,
Are there any plans on releasing a Riak Java client with Netty-4.1.x?
The reasoning for this is that some projects like Vert.x 3.3.0 for
example are already on Netty-4.1.x and AFAIK Netty's 4.1.x isn't just a
drop in replacement for 4.0.x
Would it make sense to support another Riak Java
Scenario 1: If you know the object doesn't exist or you want to
overwrite it (because allow_multi is not enabled), you want to call
withoutFetch() - there's no reason to fetch something from Riak if
it's not there (not found) or you don't care what the value is
currently (and again, are not creatin
Hi,
I have doubts about /withoutFetch()/ and /returnBody(boolean)/, I will
put some scenarios:
1. Store object (or overwrite) existing Riak object where I'm 100% I
don't need to fetch from Riak (Last write wins and goes to memory cache)
2. Apply a mutation to an object but this time return
