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

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2019/03/30 21:37:00 UTC

[jira] [Updated] (HBASE-22138) [hbase-thirdparty] Undo our direct dependence on protos in google.protobuf.Any in Procedure.proto

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

stack updated HBASE-22138:
--------------------------
    Summary: [hbase-thirdparty] Undo our direct dependence on protos in google.protobuf.Any in Procedure.proto  (was: [hbase-thirdparty] Undo our dependence on protos in google.protobuf; e.g. Timestamp, Duration...)

> [hbase-thirdparty] Undo our direct dependence on protos in google.protobuf.Any in Procedure.proto
> -------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-22138
>                 URL: https://issues.apache.org/jira/browse/HBASE-22138
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: stack
>            Priority: Major
>             Fix For: thirdparty-2.3.0
>
>
> in our shaded jar, we've bundled a few unshaded google protos. We make use of these protos in some of our core classes. What is needed is a bit of careful work undoing our dependence on these types being careful to unsure we don't break compatibility (it should be fine but needs some careful operation).
> I've targeted this at the next version of hbase-thirdparty.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)