Hi Runar,
Our current prototype of Secondary Indices works like this:
- You tell the system how to index an object by "tagging" it with
field/value pairs. The tags are passed to Riak via object metadata,
currently sent via HTTP headers. I believe this answers your main question.
- Those who woul
If what Alexander is saying is true, what you would need to do is
create your own commit hook that would look for a custom HTTP header:
X-RIAK-INDEX: {"field1": "value1", "field2": "value2"}
That hook would use that header to index on instead of the Riak
Object's value. There are limitations to
I think all that is yet to be determined, from a public standpoint (I
don't know any more than anyone not working at Basho). If secondary
indexes are implemented (interface wise) in a similar fashion as Riak
Search then I would imagine that the index would be enabled as a hook
at write time. Either
