Package: google-datacatalog-mysql-connector
google-datacatalog-mysql-connectorLibrary for ingesting MySQL metadata into Google Cloud Data Catalog.Disclaimer: This is not an officially supported Google product.Table of Contents1. Installation1.1. Mac/Linux1.2. Windows1.3. Install from source1.3.1. Get the code1.3.2. Create and activate avirtualenv1.3.3. Install the library2. Environment setup2.1. Auth credentials2.1.1. Create a service account and grant it below roles2.1.2. Download a JSON key and save it as2.2. Set environment variables3. Adapt user configurations4. Run entry point4.1. Run Python entry point4.2. Run the Python entry point with a user-defined entry resource URL prefix4.3. Run Docker entry point5 Scripts inside tools5.1. Run clean up6. Developer environment6.1. Install and run Yapf formatter6.2. Install and run Flake8 linter6.3. Run Tests7. Metrics8. Troubleshooting1. InstallationInstall this library in avirtualenvusing pip.virtualenvis a tool to
create isolated Python environments. The basic problem it addresses is one of
dependencies and versions, and indirectly permissions.Withvirtualenv, it's possible to install this library without needing system
install permissions, and without clashing with the installed system
dependencies. Make sure you use Python 3.6+.1.1. Mac/Linuxpip3installvirtualenv
virtualenv--pythonpython3.6<your-env>source<your-env>/bin/activate
<your-env>/bin/pipinstallgoogle-datacatalog-mysql-connector1.2. Windowspip3installvirtualenv
virtualenv--pythonpython3.6<your-env>
<your-env>\Scripts\activate
<your-env>\Scripts\pip.exeinstallgoogle-datacatalog-mysql-connector1.3. Install from source1.3.1. Get the codegitclonehttps://github.com/GoogleCloudPlatform/datacatalog-connectors-rdbms/cddatacatalog-connectors-rdbms/google-datacatalog-mysql-connector1.3.2. Create and activate avirtualenvpip3installvirtualenv
virtualenv--pythonpython3.6<your-env>source<your-env>/bin/activate1.3.3. Install the librarypipinstall.2. Environment setup2.1. Auth credentials2.1.1. Create a service account and grant it below rolesData Catalog Admin2.1.2. Download a JSON key and save it as<YOUR-CREDENTIALS_FILES_FOLDER>/mysql2dc-credentials.jsonPlease notice this folder and file will be required in next steps.2.2. Set environment variablesReplace below values according to your environment:exportGOOGLE_APPLICATION_CREDENTIALS=data_catalog_credentials_fileexportMYSQL2DC_DATACATALOG_PROJECT_ID=google_cloud_project_idexportMYSQL2DC_DATACATALOG_LOCATION_ID=google_cloud_location_idexportMYSQL2DC_MYSQL_SERVER=mysql_serverexportMYSQL2DC_MYSQL_USERNAME=mysql_usernameexportMYSQL2DC_MYSQL_PASSWORD=mysql_passwordexportMYSQL2DC_MYSQL_DATABASE=mysql_databaseexportMYSQL2DC_RAW_METADATA_CSV=mysql_raw_csv(IfsuppliedignorestheMYSQLservercredentials)3. Adapt user configurationsAlong with default metadata, the connector can ingest optional metadata as well, such as number of
rows in each table. The table below shows what metadata is scraped by default, and what is configurable.MetadataDescriptionScraped by defaultConfig optiondatabase_nameName of a databaseY---table_nameName of a tableY---table_typeType of a table (BASE, VIEW, etc)Y---create_timeWhen the table was createdY---update_timeWhen the table was updatedY---table_size_mbSize of a table, in MBY---column_nameName of a columnY---column_typeColumn data typeY---column_default_valueDefault value of a columnY---column_nullableWhether a column is nullableY---column_char_lengthChar length of values in a columnY---column_numeric_precisionNumeric precision of values in a columnY---ANALYZE TABLE statementStatement to refresh metadata informationNrefresh_metadata_tablestable_rowsNumber of rows in a tableNsync_row_countsSample configuration fileingest_cfg.yamlin the repository root shows what kind of configuration is expected.If you want to run optional queries, please add ingest_cfg.yaml to the directory from which you
execute the connector and adapt it to your needs.When running theANALYZE TABLEstatement, the connector credentials need INSERT privilege
in the database system tables, otherwise you will receive the following error:mysql.connector.errors.ProgrammingError: 1142 (42000): INSERT command denied to user
 'read-only'@'{HOST}' for table '{TABLE_NAME}'If it is desired to have only READ privilege make sure the flagrefresh_metadata_tablesis disabled4. Run entry point4.1. Run Python entry pointVirtualenvgoogle-datacatalog-mysql-connector\--datacatalog-project-id=$MYSQL2DC_DATACATALOG_PROJECT_ID\--datacatalog-location-id=$MYSQL2DC_DATACATALOG_LOCATION_ID\--mysql-host=$MYSQL2DC_MYSQL_SERVER\--mysql-user=$MYSQL2DC_MYSQL_USERNAME\--mysql-pass=$MYSQL2DC_MYSQL_PASSWORD\--mysql-database=$MYSQL2DC_MYSQL_DATABASE\--raw-metadata-csv=$MYSQL2DC_RAW_METADATA_CSV4.2. Run the Python entry point with a user-defined entry resource URL prefixThis option is useful when the connector cannot accurately determine the database hostname.
For example when running under proxies, load balancers or database read replicas,
you can specify the prefix of your master instance so the resource URL will point
to the exact database where the data is stored.Virtualenvgoogle-datacatalog-mysql-connector\--datacatalog-project-id=$MYSQL2DC_DATACATALOG_PROJECT_ID\--datacatalog-location-id=$MYSQL2DC_DATACATALOG_LOCATION_ID\--datacatalog-entry-resource-url-prefixproject/database-instance\--mysql-host=$MYSQL2DC_MYSQL_SERVER\--mysql-user=$MYSQL2DC_MYSQL_USERNAME\--mysql-pass=$MYSQL2DC_MYSQL_PASSWORD\--mysql-database=$MYSQL2DC_MYSQL_DATABASE\--raw-metadata-csv=$MYSQL2DC_RAW_METADATA_CSV4.3. Run Docker entry pointdockerbuild-tmysql2datacatalog.
dockerrun--rm--tty-vYOUR-CREDENTIALS_FILES_FOLDER:/datamysql2datacatalog\--datacatalog-project-id=$MYSQL2DC_DATACATALOG_PROJECT_ID\--datacatalog-location-id=$MYSQL2DC_DATACATALOG_LOCATION_ID\--mysql-host=$MYSQL2DC_MYSQL_SERVER\--mysql-user=$MYSQL2DC_MYSQL_USERNAME\--mysql-pass=$MYSQL2DC_MYSQL_PASSWORD\--mysql-database=$MYSQL2DC_MYSQL_DATABASE\--raw-metadata-csv=$MYSQL2DC_RAW_METADATA_CSV5 Scripts inside tools5.1. Run clean up# List of projects split by comma. Can be a single value without commaexportMYSQL2DC_DATACATALOG_PROJECT_IDS=my-project-1,my-project-2# Run the clean uppythontools/cleanup_datacatalog.py--datacatalog-project-ids=$MYSQL2DC_DATACATALOG_PROJECT_IDS6. Developer environment6.1. Install and run Yapf formatterpipinstall--upgradeyapf# Auto update filesyapf--in-place--recursivesrctests# Show diffyapf--diff--recursivesrctests# Set up pre-commit hook# From the root of your git project.curl-opre-commit.shhttps://raw.githubusercontent.com/google/yapf/master/plugins/pre-commit.sh
chmoda+xpre-commit.sh
mvpre-commit.sh.git/hooks/pre-commit6.2. Install and run Flake8 linterpipinstall--upgradeflake8
flake8srctests6.3. Run Testspythonsetup.pytest7. MetricsMetrics README.md8. TroubleshootingIn the case a connector execution hits Data Catalog quota limit, an error will be raised and logged with the following detailement, depending on the performed operation READ/WRITE/SEARCH:status = StatusCode.RESOURCE_EXHAUSTED
details = "Quota exceeded for quota metric 'Read requests' and limit 'Read requests per minute' of service 'datacatalog.googleapis.com' for consumer 'project_number:1111111111111'."
debug_error_string = 
"{"created":"@1587396969.506556000", "description":"Error received from peer ipv4:172.217.29.42:443","file":"src/core/lib/surface/call.cc","file_line":1056,"grpc_message":"Quota exceeded for quota metric 'Read requests' and limit 'Read requests per minute' of service 'datacatalog.googleapis.com' for consumer 'project_number:1111111111111'.","grpc_status":8}"For more info about Data Catalog quota, go to:Data Catalog quota docs.