You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2016/08/06 05:32:20 UTC

[jira] [Resolved] (HBASE-16263) Move all to do w/ protobuf -- *.proto files and generated classes -- under hbase-protocol

     [ https://issues.apache.org/jira/browse/HBASE-16263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-16263.
---------------------------
       Resolution: Fixed
     Hadoop Flags: Reviewed
    Fix Version/s: 2.0.0

Committed. Resolving.

> Move all to do w/ protobuf -- *.proto files and generated classes -- under hbase-protocol
> -----------------------------------------------------------------------------------------
>
>                 Key: HBASE-16263
>                 URL: https://issues.apache.org/jira/browse/HBASE-16263
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Protobufs
>            Reporter: stack
>            Assignee: stack
>             Fix For: 2.0.0
>
>         Attachments: HBASE-16263.master.001.patch
>
>
> To better contain our protobuf exposure, keep all to do w/ protobuffing inside the hbase-protocol module.
> This task moves rest, examples, and server proto files that do testing and CP endpoints etc., under hbase-protocol. The patch is big but it is all just moving files.
> interesting to see the copy-paste being done everywhere of proto generation. For this reason alone, it is better to have all the protos in the one place beside doc on how-to, etc.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)