Yeah, in attempt number two the index names and values have been url encoded
when creating the relevant HTTP headers and when doing the index fetch the
index name and value are again encoded.
What is probably happening is that Riak will decode the incoming fetch url and
then use the decoded va
I know, that's the reason why I thought it was probably best to encode the
values coming in because otherwise I would have to reject any value coming into
my client if it would contain spaces or (especially) commas.
Unfortunately an index fetch (url encoded both name and value) will then never
Hi Age,
One thing to consider is that Riak allows a secondary index to have multiple
values. I can e.g. create an object with two values for a integer secondary
index as follows:
curl -X PUT -H "Content-Type: text/plain" -H 'x-riak-index-idx_int: 12'
-H 'x-riak-index-idx_int: 13' -d 'd
Question about 2) -- are you also encoding the index names and values when
issuing the fetch? (Maybe post some example code or Riak object header
snippets, and examples of the fetch queries, that might help).
On Wed, Feb 20, 2013 at 3:56 PM, Age Mooij wrote:
> Hi all,
>
> I'm writing a new Scala
