cdap | open source framework for building data

To fix this problem I had to migrate gitlab-secrets.json from /etc/gitlab too, because this file contains the database encryption key, CI/CD variables, and variables used for two-factor authentication.
If you fail to restore this encryption key file along with the application data backup, users with two-factor authentication enabled and GitLab Runner lose access to your GitLab server.

after a lot of testing i changed the storage class i installed rook-ceph using : this procedure note: you have to change the image version in cluster.yaml from ceph/ceph:v14.2.4 to ceph/ceph:v16

I make a bit of research, and it led me to this github issue: https://github.com/Azure/aks-engine/issues/1494

SMB mount options(including dir permission) could not be changed, it's by SMB proto design, while for disk(ext4, xfs) dir permission could be changed after mount close this issue, let me know if you have any question.

From what I see, there are no options chown after mounting it.

BUT

I also find a workaround that might apply to your issue: https://docs.openshift.com/container-platform/3.11/install_config/persistent_storage/persistent_storage_azure_file.html

It's Workaround for using MySQL with Azure File for Openshift, but I think it could work with your case.

CDAP should run in Java version 8. So once you download JDK, set the Java home like

Which version of Datafusion are you running? Also what is the amount of memory for the Dataproc cluster? Sometimes we observe this issue when the Dataproc cluster ran out of memory. I would suggest increasing the amount of memory.

This is happening because of having additional , characters within the quoted string. As of now we do not support CSV with quoted fields having delimiter. If this is just a test input, I suggest you to try with string values that do not have , within. Null values are supported and should work as expected.

I have created a bug for this.

This error is related to the lack of Service Account user role (roles/iam.serviceAccountUser) associate to the user/service account used to run the DataProc job.

In order to overcome this error, you need to go to the IAM Policy Console and give the Service Account User role, as described here, to the current user/service account you are using to run the job. As exemplified below:

1. Go to the IAM & Admin Console
2. Click on IAM
3. Select the member you are using to run your job
4. Click on the pen icon in the right side of the member's info
5. Add the Service Account user role

Pointing out some important topics, service accounts are used to make authorised API calls, through the service account itself or through delegated users within it. Moreover, about impersonation service accounts, an user with particular permissions can act as another service account with the necessary permission to execute a specific job.

Note: in step 3, you can also give to a particular user(email) the roles/iam.serviceAccountUser by clicking on +ADD (in top of the console). Then, writing the email and selecting the permission. Although, I must stress that this permission would be given at a project level. Thus, this user will be able to impersonate any of the existent Service Accounts.

Since the project of the Enterprise Edition of Cloud Data Fusion is different, you need to make sure that the account you logged in the gcloud has the correct permission to the Cloud Data Fusion instance. You need to grant the service account with the roles/datafusion.viewer.

You can read more about access control here

Assuming your bucket is publicly accessible, then the URL you want to provide to the argument setter have the following pattern: