> On Jan 27, 2015, at 5:46 AM, Santi Kumar wrote:
>
> HI Chris
> I cant send the code publicly so I tested with couple more examples.If I
> annotate the field with "secretKey" or "authSecret", then those field values
> are becoming null in the object.
>
> If I change the key with "indexKey" o
HI Chris
I cant send the code publicly so I tested with couple more examples.If I
annotate the field with "secretKey" or "authSecret", then those field
values are becoming null in the object.
If I change the key with "indexKey" or some thing then it's part of the
object state. I have modified acco
> On Jan 26, 2015, at 5:48 PM, Santi Kumar wrote:
>
> Yes. I'm using POJO and annotating one of the field with RiakIndex. When I'm
> reading the object with the key, as the tag field is not part of the object,
> while writing I dont have the tag value while writing the object.
>
> Class Foo {
Yes. I'm using POJO and annotating one of the field with RiakIndex. When
I'm reading the object with the key, as the tag field is not part of the
object, while writing I dont have the tag value while writing the object.
Class Foo {
private String fooId;
@RiakIndex(name="barid")
private String b
> On Jan 26, 2015, at 09:45, Santi Kumar wrote:
>
> Hi
> I'm defining a field of an object as 2i index with @RiakIndex. While creating
> the object I initialised both the values and stored the object against the
> key of that object and stored against the index.
>
> In a separate thread anot
Hi
I'm defining a field of an object as 2i index with @RiakIndex. While
creating the object I initialised both the values and stored the object
against the key of that object and stored against the index.
In a separate thread another field of the object is updated where I dont
have handle to the 2
