|
@@ -0,0 +1,42 @@
|
|
|
+---
|
|
|
+title: "GDPR in Ozone"
|
|
|
+date: "2019-September-17"
|
|
|
+weight: 5
|
|
|
+summary: GDPR in Ozone
|
|
|
+icon: user
|
|
|
+---
|
|
|
+<!---
|
|
|
+ Licensed to the Apache Software Foundation (ASF) under one or more
|
|
|
+ contributor license agreements. See the NOTICE file distributed with
|
|
|
+ this work for additional information regarding copyright ownership.
|
|
|
+ The ASF licenses this file to You under the Apache License, Version 2.0
|
|
|
+ (the "License"); you may not use this file except in compliance with
|
|
|
+ the License. You may obtain a copy of the License at
|
|
|
+
|
|
|
+ http://www.apache.org/licenses/LICENSE-2.0
|
|
|
+
|
|
|
+ Unless required by applicable law or agreed to in writing, software
|
|
|
+ distributed under the License is distributed on an "AS IS" BASIS,
|
|
|
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
|
+ See the License for the specific language governing permissions and
|
|
|
+ limitations under the License.
|
|
|
+-->
|
|
|
+
|
|
|
+
|
|
|
+Enabling GDPR compliance in Ozone is very straight forward. During bucket
|
|
|
+creation, you can specify `--enforcegdpr=true` or `-g=true` and this will
|
|
|
+ensure the bucket is GDPR compliant. Thus, any key created under this bucket
|
|
|
+will automatically be GDPR compliant.
|
|
|
+
|
|
|
+GDPR can only be enabled on a new bucket. For existing buckets, you would
|
|
|
+have to create a new GDPR compliant bucket and copy data from old bucket into
|
|
|
+ new bucket to take advantage of GDPR.
|
|
|
+
|
|
|
+Example to create a GDPR compliant bucket:
|
|
|
+
|
|
|
+`ozone sh bucket create --enforcegdpr=true /hive/jan`
|
|
|
+
|
|
|
+`ozone sh bucket create -g=true /hive/jan`
|
|
|
+
|
|
|
+If you want to create an ordinary bucket then you can skip `--enforcegdpr`
|
|
|
+and `-g` flags.
|