@TJC - you should be interested in these changes 😄

These changes look good to me ... not that I know 100% what they do 😄

👍

@TJC - Do you have any Scala code that I could test these changes against, or that show the trouble you were having with the raw types?

Create demo.scala:

package foo

import com.basho.riak.client.core.query.RiakObject
import com.basho.riak.client.core.util.BinaryValue
import com.basho.riak.client.core.query.indexes.StringBinIndex

class RiakTest {

  val obj = new RiakObject
  obj.setValue(BinaryValue.create("hello world"))
  obj.setContentType("application/json")

  val idxtype = StringBinIndex.named("myindex")
  val indexes = obj.getIndexes
  indexes.getIndex(idxtype).add("myvalue")

}

Try to compile it with:
scalac -classpath riak-client-2.0.3.jar:netty-all-4.0.33.Final.jar demo.scala

I can make a version that uses sbt to get the dependencies and so forth, but I figured that the smallest, simplest demo was best. It doesn't actually do anything when compiled, but the compilation failure is the test.

@TJC Thanks!

So good news and bad news.

Good news:
You can get it to work by being explicit with the types on getIndex():
indexes.getIndex[StringBinIndex,StringBinIndex.Name](idxtype).add("myvalue")

Bad news:
No matter how much cleanup I do to the type system between RiakIndex, RiakIndex.Name, and RiakIndexes.[get|has|remove]index(), I cannot get Scala to infer the types correctly.

I even tried being more explicit and giving Name an extra type parameter to hint at what it's main type parameter that extends RiakIndex is : `>-><V, U extends RiakIndex>`

But Scala just laughed and said it couldn't match another type parameter.

I'll keep the <?> additions I made becuase they are more correct even if Java don't care, and then we'll have to make a note for Scala users to be explicit about the types for getIndex(). 😭

Thanks for trying!