Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 30 Jun 2017 01:18:00 +0000 (UTC)
From: "Alex Araujo (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13047814.1488490839000.140656.1498785480274@Atlassian.JIRA>
In-Reply-To: <JIRA.13047814.1488490839000@Atlassian.JIRA>
References: <JIRA.13047814.1488490839000@Atlassian.JIRA> <JIRA.13047814.1488490839994@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HBASE-17721) Provide streaming APIs with
 SSL/TLS
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 30 Jun 2017 01:18:08 -0000


    [ https://issues.apache.org/jira/browse/HBASE-17721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16069297#comment-16069297 ] 

Alex Araujo commented on HBASE-17721:
-------------------------------------

I've been following HBASE-18240. Last time I tried to shade grpc, com.google.code.findbugs:jsr305 was pulled in transitively and the build failed due to the HBASE-16321 restriction. I'll take another look soon.
Assuming it's still a transitive dep, would we allow jsr305 transitively in hbase-thirdparty? [~busbey] might be able to tell us.

> Provide streaming APIs with SSL/TLS
> -----------------------------------
>
>                 Key: HBASE-17721
>                 URL: https://issues.apache.org/jira/browse/HBASE-17721
>             Project: HBase
>          Issue Type: Umbrella
>          Components: rpc, security
>            Reporter: Alex Araujo
>            Assignee: Alex Araujo
>             Fix For: 2.0.0
>
>
> Umbrella to add optional client/server streaming capabilities to HBase.
> This would allow bandwidth to be used more efficiently for certain operations, and allow clients to use SSL/TLS for authentication and encryption.
> Desired client/server scaffolding:
> - HTTP/2 support
> - Protocol negotiation (blocking vs streaming, auth, encryption, etc.)
> - TLS/SSL support
> - Streaming RPC support
> Possibilities (and their tradeoffs):
> - gRPC: Some initial work and discussion on HBASE-13467 (Prototype using GRPC as IPC mechanism)
> -- Has most or all of the desired scaffolding
> -- Adds additional g* dependencies. Compat story for g* dependencies not always ideal
> - Custom HTTP/2 based client/server APIs
> -- More control over compat story
> -- Non-trivial to build scaffolding; might reinvent wheels along the way
> - Others?
> Related Jiras that might be rolled in as sub-tasks (or closed/replaced with new ones):
> HBASE-17708 (Expose config to set two-way auth over TLS in HttpServer and add a test)
> HBASE-8691 (High-Throughput Streaming Scan API)
> HBASE-14899 (Create custom Streaming ReplicationEndpoint)


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)