[jira] [Commented] (HADOOP-17544) Mark KeyProvider as Stable

["Akira Ajisaka (Jira)" <ji...@apache.org>]

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

Akira Ajisaka commented on HADOOP-17544:
----------------------------------------

FYI: LinkedIn used the KeyProvider interface to integrate the company's internal service.
 [https://engineering.linkedin.com/blog/2021/the-exabyte-club--linkedin-s-journey-of-scaling-the-hadoop-distr]
{quote}LinkedIn has its own key management service, LiKMS, which is the only service certified and approved for managing cryptographic keys and secrets internally. We used pluggable interfaces such as KeyProvider supported by HDFS to integrate LiKMS with transparent encryption at rest.
{quote}

> Mark KeyProvider as Stable
> --------------------------
>
>                 Key: HADOOP-17544
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17544
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: security
>            Reporter: Akira Ajisaka
>            Assignee: Akira Ajisaka
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Now, o.a.h.crypto.key.KeyProvider.java is marked Public and Unstable. I think the class is very stable, and it should be annotated as Stable.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org