Hello dear riak list.
Could you clarify my observation.
Recently we had an issue with corrupted data on riak. Instance was powered
off and after it became available we found some bad_crc errors in logs. At
that moment we had 1.2.1-1 riak nodes in our cluster. After some googling we
found an issue
If I declare @RiakKey and 2i indexes (@RiakIndex) for some fields in my
Item class, then those fields will not be displayed when querying the
record over the browser (ie. http://localhost/riak/myBucket/myKey1).
I have tried adding the annotation @JSONInclude but does not seem to change
the
No; they are explicitly excluded from serialization because they're metadata.
The 2i indexes are returned in the http headers, and the key you kinda
already have to know to make the query in the first place.
Thanks,
Roach
On Thu, Aug 22, 2013 at 9:32 AM, mex cnasi...@gmail.com wrote:
If I
Create a pseudo getters for the 2i indexes, valid return types are:
String, Long (And Integer) and Set of any of the mentioned, the benefit
of this is the fact that your 2i indexes are not actual properties, they
are meant to be computation of something, example:
/public class Postcode {//
Hi Thomas,
Yes you can change the n_val in the default bucket properties of the riak
cluster. That's how CS determines how many replicas to store. However,
please keep in mind that reducing the replicas can reduce your availability.
-Andrew
On Wed, Aug 21, 2013 at 5:27 AM, Thomas Dunham
Hi Jon,
Thanks for your response. Unfortunately it is not as simple as that... in this
particular case, I have a large dataset of predefined objects (with ranges
already defined). I then need to perform the lookups given specific values.
Unfortunately the ranges are not uniform e.g. domain
How about using a 2i range query with pagination using max_results=1? Such
results are ordered, so it's effectively an open ended query-for-first after N,
if you choose a large end value for the range.
Kresten
Sent from my iPhone
On 22/08/2013, at 22.38, Y N
Idan,Actually in the case you described of using a 3 node Riak cluster with n_val of 2 the behavior you see makes perfect sense. When using only three nodes Riak does not guarantee that all replicas of an object will be on distinct physical nodes. So if you have one node down you can hit a case
Hi Kresten,
Thanks for the response... I was thinking about this for a bit... and unless
I'm missing something (or don't quite understand how 2i or search works), I
don't think 2i or search will solve this problem. I may need to fall back to
basic M/R for this.
Correct me if I'm wrong, but
