[
https://issues.apache.org/jira/browse/HBASE-7224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13539336#comment-13539336
]
stack commented on HBASE-7224:
------------------------------
bq. Should we remove these as part of this patch is a question. I had raised
HBASE-6521 a while back for addressing the versioning in the new PB world.
Lets do the fixup in hbase-6521. I made it a blocker on 0.96. As you say,
what is there now makes no sense.
So, this patch is good enough to close out this issue? Let me post on rb.
> Remove references to Writable in the ipc package
> ------------------------------------------------
>
> Key: HBASE-7224
> URL: https://issues.apache.org/jira/browse/HBASE-7224
> Project: HBase
> Issue Type: Sub-task
> Components: IPC/RPC, Protobufs
> Reporter: Devaraj Das
> Assignee: stack
> Priority: Blocker
> Fix For: 0.96.0
>
> Attachments: 7224.txt, 7224v2.txt, 7224v3.txt, 7224v4.txt,
> purge_more_writables.txt
>
>
> I see references to Writable in the ipc package, most notably in the
> Invocation class. This class is not being used that much in the core ipc
> package but used in the coprocessor protocol implementations (there are some
> coprocessor protocols that are Writable based still). This jira is to track
> removing those references and the Invocation class (once HBASE-6895 is
> resolved).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
