Ruby content.meta does not correctly apply X-Riak-Meta- prefix [JIRA: CLIENTS-1109]

[mikedotson]

Ruby content.meta does not correctly apply X-Riak-Meta- prefix [JIRA: CLIENTS-1109]

[lukebakken]

Best bug report ever! Thanks!

[lukebakken]

The only place in the Ruby client code that X-Riak-Meta-* is specially handled is here. This is when an object is loaded from map/reduce. I don't see special handling anywhere else in the Ruby code, nor in the Java or Python clients. I am searching the Riak code itself to see how X-Riak-Meta-* is handled, both by the HTTP and PB interfaces.

[lukebakken]

@mikedotson - Since the Ruby client is protobuf-only, we send user metadata in the usermeta field of RpbContent. Riak just stuffs the data from here into the object it stores. There are no headers involved, because it's protobuf.

When an HTTP client posts data to Riak's HTTP API, the only way Riak "knows" that the header is for user metadata is via the X-Riak-Meta- header. So, when you post data via HTTP using that header, Riak stores it in the user metadata part of the object, and also uses that header on HTTP retrieval of that object.

As you can see in your examples, Riak doesn't prepend X-Riak-Meta- to the Version value when it is retrieved via the HTTP interface. That is because the value stored with the Riak object is what is passed in - Version through the protobuf store operation, X-Riak-Meta-Version via the HTTP store operation.

In short, if you want to have the X-Riak-Meta- prefix on an HTTP or PB get, you must store it with that prefix from your client.