Hi all,

   I will submit some pr for this  pip , if you have any questions or 
suggestions, please give me the  feedback. Thank you
    




| |
Jun Zhang
|
|
[email protected]
|


---- Replied Message ----
| From | Jun Zhang<[email protected]> |
| Date | 10/11/2023 22:18 |
| To | [email protected]<[email protected]> |
| Cc | [email protected]<[email protected]> |
| Subject | Re: [DISCUSS] PIP-11:Introduce Encryption Capability for Paimon |




Hi, Jingsong, YONG FANG:


I update the document follow your suggestion,could you help me review again ? 
Thanks.




| |
Jun Zhang
|
|
[email protected]
|


---- Replied Message ----
| From | Jingsong Li<[email protected]> |
| Date | 10/11/2023 11:16 |
| To | <[email protected]> |
| Subject | Re: [DISCUSS] PIP-11:Introduce Encryption Capability for Paimon |
Hi Jun,

I think you can enrich the Motivation part. What is the user case you
want to solve? And you can list some designs from other storages, What
problem have they solved?

Best,
Jingsong

On Wed, Oct 11, 2023 at 11:03 AM YONG FANG <[email protected]> wrote:

Hi Jun,

Can you give more details about where the encryption would be used in
Paimon? On the other hand, what's the level of the encryption in paion,
record or data file or table or entire catalog?


On Tue, Oct 10, 2023 at 10:59 PM Jun Zhang <[email protected]> wrote:





Hi all,

I want to bring up a discussion about PIP-11:Introduce Encryption
Capability for Paimon[1].


With the development of enterprises, data security has become increasingly
important, and there are some industries that have mandatory legal
requirements for it, such as bank, transportation, etc. As a data lake
framework, it is very important for paimon in supporting data encryption to
meet enterprise security standards. We should extend the current paimon
architecture to provide users with out-of-the-box encryption capabilities.


Looking forward to your feedback, thanks!


[1].
https://cwiki.apache.org/confluence/display/PAIMON/PIP-11%3AIntroduce+Encryption+Capability+for+Paimon


| |
Jun Zhang
|
|
[email protected]
|


Reply via email to