This is a remnant from initial plans to do single-RPC-per-RS batching of
coprocessor RPCs via the parameterized
Currently we do a single RPC per region for HTable.coprocessorExec()
processBatchCallback() takes a List<? extends Row>, hence the "implements"
I had originally planned on doing this enhancement (there was one hurdle in
scoping of some vars within ExecRPCInvoker as I recall), but obviously
haven't gotten around to it, so feel free to remove the Row implementation.
I don't think it's needed for the current
I don't really agree that this is a big issue of confusion though. Exec is
part of the internal implementation and referenceRow has local javadoc.
Exec class javadoc also references HTable.coprocessorExec javadoc, which
goes to lengths to explain how the row key is used. But, again, the Row
implementation isn't currently used, so it's just dead weight. Feel free to
On Wed, Apr 27, 2011 at 10:06 PM, Stack wrote:
I took a look. Could not figure it out. I think 'reference row'
needs to be explained better (or implementation of Row Interface
removed -- gives impression that CP is row scoped; I don't think that
On Wed, Apr 27, 2011 at 9:08 PM, Himanshu Vashishtha
Its not clear why org.apache.hadoop.hbase.client.coprocessor.Exec
Row interface. It seems the row attribute is not used as such apart from
passing it to server side as a part of Exec object. Is this intentional or I
am missing something.
Though its comparatively older code now, but still would be good to know the