[
https://issues.apache.org/jira/browse/HBASE-7224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13539179#comment-13539179
]
Devaraj Das commented on HBASE-7224:
------------------------------------
bq. The Writables that remain are in HBaseServer answering SASL, which seems
harmless,
Yeah they seem harmless, and the usage of Writable here is probably never going
to change (the writable there is BytesWritable, and that's a very simple
wrapper around bytes).
bq. then there is the VersionedProtocol stuff. Can we get rid of this stuff?
The ProtocolSignature stuff? It is Writables based. Should we do it in a
different issue as part of the rpc rejiggering?
We should decide what to do about the versioning/signature. Currently, this
stuff is not used in any meaningful way and can be removed. 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.
> 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: Devaraj Das
> Priority: Blocker
> Fix For: 0.96.0
>
> Attachments: 7224.txt, 7224v2.txt, 7224v3.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
