[
https://issues.apache.org/jira/browse/HBASE-7533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-7533:
-------------------------
Attachment: 7533v4.txt
Refactor in RPC.proto to accomodate Elliott feedback. See diff for description
of the protocol.
Trying to miniize change. Not too different from previous patches. Just has
more failed unit
tests fixed.
Still missing is the TODO EncodedDataBlock though at Matt Corgan suggestion and
looking back at
my old patch in HBASE-7233, Seializing KeyValues, this instead will just be
bytes produced by
a CellOutputStream and then read with a CellScanner.java -- two simple Cell
Interfaces). Let
me try and get a basic implementation in and then call this patch quits.
Now if you enable ipc logging you see the complete client side request and over
on server
the complete receive and then what it writes on the wire. Its over the top but
nice debugging.
It is only on if you enable debug. Will work on a custom pb TextFormatter that
doesn't output
it all -- that has some bounds -- after this patch goes in. Need to make it so
this toString
shows up in the UI to where we show process listing.
Renamed some methods in rpc so matches spec and so its clearer whats going on
in here.
Effort to avoid buffer creations and oversized buffer creations by pb.
Removed unused classes // Call and moved some inner classes out to be package
protected
standalones such as QosFunction and MethodCache. This is the bulk of the patch.
> Write an RPC Specification for 0.96
> -----------------------------------
>
> Key: HBASE-7533
> URL: https://issues.apache.org/jira/browse/HBASE-7533
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Assignee: stack
> Fix For: 0.96.0
>
> Attachments: 7533_proto_sketch.txt, 7533v4.txt, rpc_spec3.txt,
> rpc_spec.txt
>
>
> RPC format is changing for 0.96 to accomodate our protobufing all around.
> Here is a first cut. Please shred:
> https://docs.google.com/document/d/1-1RJMLXzYldmHgKP7M7ynK6euRpucD03fZ603DlZfGI/edit
--
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
