hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Araujo (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17721) Provide streaming APIs with SSL/TLS
Date Tue, 04 Apr 2017 21:03:41 GMT

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

Alex Araujo commented on HBASE-17721:

I was able to compile existing protos and grpc protos within hbase-protocol-shaded using grpc
1.1.2 and protobuf 3.1.0. I got hung up on shading grpc and its dependencies (grpc-core depends
on com.google.code.findbugs:jsr305, which HBase does not allow). [~apurtell] suggested building
a grpc-shaded module outside of HBase and pulling it in as a dependency rather than building
it. I was planning on trying that or punting on shading grpc for the time being to get some
benchmarks for HBASE-13467. Given other priorities, I'll likely get to that in a couple of

> 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
> -- 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

View raw message