[
https://issues.apache.org/jira/browse/HBASE-16308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15414766#comment-15414766
]
stack commented on HBASE-16308:
-------------------------------
v13 Fix fact that I was not initializing RpcController in ScannerCallable.
> Contain protobuf references
> ---------------------------
>
> Key: HBASE-16308
> URL: https://issues.apache.org/jira/browse/HBASE-16308
> Project: HBase
> Issue Type: Sub-task
> Components: Protobufs
> Reporter: stack
> Assignee: stack
> Fix For: 2.0.0
>
> Attachments: HBASE-16308.master.001.patch,
> HBASE-16308.master.002.patch, HBASE-16308.master.003.patch,
> HBASE-16308.master.004.patch, HBASE-16308.master.005.patch,
> HBASE-16308.master.006.patch, HBASE-16308.master.006.patch,
> HBASE-16308.master.007.patch, HBASE-16308.master.008.patch,
> HBASE-16308.master.009.patch, HBASE-16308.master.010.patch,
> HBASE-16308.master.011.patch, HBASE-16308.master.012.patch,
> HBASE-16308.master.013.patch
>
>
> Clean up our protobuf references so contained to just a few classes rather
> than being spread about the codebase. Doing this work will make it easier
> landing the parent issue and will make it more clear where the division
> between shaded protobuf and unshaded protobuf lies (we need to continue with
> unshaded protobuf for HDFS references by AsyncWAL and probably EndPoint
> Coprocessors)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
