Getting error while running "Install necessary types into your Purview instance by running the following commands in Bash."

[rahul7thube]

Describe the bug
We are installing/configuring Purview ADB Lineage Solution Accelerator for our Dev Purview account in connector only deployment mode. While executing the post installation step3 "Install necessary types into your Purview instance by running the following commands in Bash." we are getting below error.

Post installation Step 3: (Executed from cloud bash shell)
purview_endpoint="https://<enter_purview_account_name>.purview.azure.com"
TENANT_ID="<TENANT_ID>"
CLIENT_ID="<CLIENT_ID>"
CLIENT_SECRET="<CLIENT_SECRET>"

acc_purview_token=$(curl https://login.microsoftonline.com/$TENANT_ID/oauth2/token --data "resource=https://purview.azure.net&client_id=$CLIENT_ID&client_secret=$CLIENT_SECRET&grant_type=client_credentials" -H Metadata:true -s | jq -r '.access_token')
purview_type_resp_custom_type=$(curl -s -X POST $purview_endpoint/catalog/api/atlas/v2/types/typedefs
-H "Authorization: Bearer $acc_purview_token"
-H "Content-Type: application/json"
-d @Custom_Types.json )

echo $purview_type_resp_custom_type

====================================================================================
Error:
{"requestId":"35a7792a-dad5-4ba5-b5c5-d0a84904ce58","errorCode":"ATLAS-400-00-01A","errorMessage":"invalid parameters: invalid payload, expect schemaAttributes in purview_custom_connector_generic_column should be list of string, but found: data_type"}

======================================================================================
Additional details:

1. we are using latest release tag for cloning the git repo.
   git clone -b 2.3.1 https://github.com/microsoft/Purview-ADB-Lineage-Solution-Accelerator.git
2. Also we tried to clone repo from old versions but the Custom_Types.json is same for all versions

Please let us know if you need any further information

[kunr0747]

Hello, we are facing same issue, expecting a fix as soon as possible.

[rvalente-bi4all]

I had the same issue and, after looking into "deployment/infra/Custom_Types.json" file and Apache Atlas documentation found a fix.
Just change "schemaAttributes": "data_type" to "schemaAttributes": "[\"data_type\"]".
Hope that solves the problem!

[davidkhala]

pending merge of #235