[ https://issues.apache.org/jira/browse/HUDI-2370 ]


    Raymond Xu deleted comment on HUDI-2370:
    ----------------------------------

was (Author: githubbot):
hudi-bot commented on pull request #3614:
URL: https://github.com/apache/hudi/pull/3614#issuecomment-914114290


   <!--
   Meta data
   {
     "version" : 1,
     "metaDataEntries" : [ {
       "hash" : "5456ff21918353639272de85422285da4aec02e4",
       "status" : "UNKNOWN",
       "url" : "TBD",
       "triggerID" : "5456ff21918353639272de85422285da4aec02e4",
       "triggerType" : "PUSH"
     } ]
   }-->
   ## CI report:
   
   * 5456ff21918353639272de85422285da4aec02e4 UNKNOWN
   
   <details>
   <summary>Bot commands</summary>
     @hudi-bot supports the following commands:
   
    - `@hudi-bot run travis` re-run the last Travis build
    - `@hudi-bot run azure` re-run the last Azure build
   </details>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


> Supports data encryption
> ------------------------
>
>                 Key: HUDI-2370
>                 URL: https://issues.apache.org/jira/browse/HUDI-2370
>             Project: Apache Hudi
>          Issue Type: New Feature
>            Reporter: liujinhui
>            Assignee: liujinhui
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 0.11.0
>
>
> Data security is becoming more and more important, if hudi can support 
> encryption, it is very welcome
> 1. Specify column encryption
>  2. Support footer encryption
>  3. Custom encrypted client interface(Provide memory-based encryption client 
> by default)
> 4. Specify the encryption key
>  
> When querying, you need to pass the relevant key or obtain query permission 
> based on the client's encrypted interface. If it fails, the result cannot be 
> returned.
>  1. When querying non-encrypted fields, the key is not passed, and the data 
> is returned normally
>  2. When querying encrypted fields, the key is not passed and the data is not 
> returned
>  3. When the encrypted field is queried, the key is passed, and the data is 
> returned normally
>  4. When querying all fields, the key is not passed and no result is 
> returned. If passed, the data returns normally
>  
> Start with COW first



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to