Hi Is there any reason why TableOperations.getSplits() does not expose the location information (the information about tablet-to-tserver correspondence) ? It has this information internally and then just drops it.
This information can be useful to perform scans a bit smarter (to maximize parallelism while avoiding overloading a single tserver) and it also can be provided to Spark RDD. Yes, I can call MetadataTable.getEntries() instead of TableOperations.getSplits(), but, first, this API looks more 'internal' and, second, it needs the copy of credentials, thus making the credential management a bit complicated.
