Multi backend not returning "indexes_not_supported" when expected [JIRA: RIAK-2360]

[lukebakken]

Riak 2.1.3 devrel, built with Erlang basho/otp OTP_R16B02_basho10rc2

Following the examples here: http://docs.basho.com/riak/latest/dev/using/2i/#Examples

Reproduction script is attached: test-2i.txt

Please create a bucket type named people using the leveldb backend (or use leveldb as the default Riak backend)

Output:

$ ./test-2i
SHOULD ONLY RETURN LARRY:
{"keys":["veronica","curly","larry","moe"]}
SHOULD ONLY RETURN VERONICA:
{"keys":["veronica","moe","curly","larry"]}

Output when using a bucket type configured to use the memory backend:

$ ./test-2i.txt
SHOULD ONLY RETURN LARRY:
{"keys":["larry"]}
SHOULD ONLY RETURN VERONICA:
{"keys":["veronica"]}

[lukebakken]

@JeetKunDoug @jonmeredith - This only happens when typed buckets are used. I just added basho/riak_test#981 to begin adding tests. I added a test that does not use types, and will add typed tests going forward.

[hazen]

@lukebakken I'm assuming this problem exists back in 2.0, right? I assume we'll want this for the next 2.0 release then, too, @JeetKunDoug? Just making sure the fix lands in the right place.

[lukebakken]

@JeetKunDoug @javajolt - this gets even more interesting. I just ran test-2i against the devrel set up via riak_test and the script ran fine. The default backend for the devrel was eleveldb, as opposed to the multi backend I have been using. I am going to set up 2.1.3 with eleveldb as the default to see what happens.

[JeetKunDoug]

Hrm - so perhaps the multi-backend is the real culprit... interesting. Thank you for continuing to try to figure this out.

[lukebakken]

OK it gets even better.

• Originally, I used this script to set up bucket types for the Riak Docs code examples I was working on.
• While working on this code example I noticed that I would get multiple keys back, which prompted me to write the test-2i script I have attached here.
• When I set up riak_test to run the 2i and bucket_type tests, I configured Riak to use eleveldb as the default backend, and everything works, even test-2i
• I just now set up my 2.1.3 cluster to use eleveldb as the default backend, and test-2i runs successfully.
• You'll notice in the setup-examples script that the indexes type is not set to use eleveldb as the backend. AHA, that oversight is what lead to this entire thing. BUT, when you try to index an object via a backend that does not support it, you are supposed to get an error from Riak. In my case, the objects saved to the indexes type just fine with secondary index metadata. There is still something going on, but not as serious as I thought.

[lukebakken]

If I have my cluster set to use bitcask as the default backend, and try to store an object with index data, I get this error, which is expected:

RiakError|0|{error,{indexes_not_supported,riak_kv_bitcask_backend}}

If I use multi backend with bitcask as the default, and save the same objects with index data to a type that is using the default backend, I do not get the same error.