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


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

was (Author: githubbot):
vinothchandar commented on a change in pull request #3614:
URL: https://github.com/apache/hudi/pull/3614#discussion_r703906345



##########
File path: pom.xml
##########
@@ -91,7 +91,7 @@
     <kafka.version>2.0.0</kafka.version>
     <confluent.version>5.3.4</confluent.version>
     <glassfish.version>2.17</glassfish.version>
-    <parquet.version>1.10.1</parquet.version>
+    <parquet.version>1.12.0</parquet.version>

Review comment:
       main thing is the parquet upgrade. Would this be compatible with Spark 
2.x. guess not? I think this needs Spark 3.2? 
   https://github.com/apache/spark/blob/branch-3.2/pom.xml 
   
   this will also upgrade `parquet-avro` that we use everywhere. So just 
thinking about that. 
   
   




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