Google Cloud MySQL

Specify Google Cloud MySQL Connection Settings

Perform the following steps to configure Google Cloud MySQL as a Source in Hevo:

1. Click PIPELINES in the Navigation Bar.

2. Click + CREATE PIPELINE in the Pipelines List View.

3. On the Select Source Type page, select Google Cloud MySQL.

4. On the Configure your Google Cloud MySQL Source page, specify the following:

   

   • Pipeline Name: A unique name for your Pipeline, not exceeding 255 characters.

   • Database Host: The MySQL host’s IP address or DNS.

     The following table lists a few examples of MySQL hosts:

     Variant	Host
     Amazon RDS MySQL	mysql-rds-1.xxxxx.rds.amazonaws.com
     Azure MySQL	mysql.database.windows.net
     Generic MySQL	10.123.10.001 or mysql-replica.westeros.inc
     Google Cloud MySQL	35.220.150.0

     Note: For URL-based hostnames, exclude the http:// or https:// part. For example, if the hostname URL is http://mysql-replica.westeros.inc, enter mysql-replica.westeros.inc.

   • Database Port: The port on which your Google Cloud MySQL server listens for connections. Default value: 3306.

   • Database User: The authenticated user who has the permissions to read tables in your database.

   • Database Password: The password for the database user.

   • Select an Ingestion Mode: The desired mode by which you want to ingest data from the Source. You can expand this section by clicking SEE MORE to view the list of ingestion modes to choose from. Default value: BinLog. The available ingestion modes are BinLog, Table, and Custom SQL.

     

     Depending on the ingestion mode you select, you must configure the objects to be replicated. Refer to section, Object and Query Mode Settings for the steps to do this.

     Note: For Custom SQL ingestion mode, all Events loaded to the Destination are billable.

   • Database Name: The database you want to load data from if the Pipeline mode is Table or Custom SQL.

   • Connection Settings

     • Connect through SSH: Enable this option to connect to Hevo using an SSH tunnel, instead of directly connecting your MySQL database host to Hevo. This provides an additional level of security to your database by not exposing your MySQL setup to the public. Read Connecting Through SSH.

       If this option is disabled, you must whitelist Hevo’s IP addresses. Refer to the content for your MySQL variant for steps to do this.

     • Use SSL: Enable it to use SSL encrypted connection. To enable this, specify the following:

       • CA File: The file containing the SSL server certificate authority (CA).

         • Load all CA Certificates: If selected, Hevo loads all CA certificates (up to 50) from the uploaded CA file, else it loads only the first certificate.

           Note: Select this check box if you have more than one certificate in your CA file.

       • Client Certificate: The client public key certificate file.

       • Client Key: The client private key file.

   • Advanced Settings

     • Load All Databases: Applicable for Pipelines with BinLog mode. If this option is enabled, Hevo loads the data from all databases on the selected host. Else, specify a comma-separated list of Database Names you want to load data from.

     • Load Historical Data: Applicable for Pipelines with BinLog mode. If this option is enabled, the entire table data is fetched during the first run of the Pipeline. If disabled, Hevo loads only the data that was written in your database after the time of creation of the Pipeline.

     • Merge Tables: Applicable for Pipelines with BinLog mode. If this option is enabled, Hevo merges tables with the same name from different databases while loading the data to the warehouse. Hevo loads the Database Name field with each record. If disabled, the database name is prefixed to each table name. Read How does the Merge Tables feature work?.

     • Include New Tables in the Pipeline: Applicable for all ingestion modes except Custom SQL.

       If enabled, Hevo automatically ingests data from tables created in the Source after the Pipeline has been built. These may include completely new tables or previously deleted tables that have been re-created in the Source.

       If disabled, new and re-created tables are not ingested automatically. They are added in SKIPPED state in the objects list, on the Pipeline Overview page. You can update their status to INCLUDED to ingest data. You can include these objects post-Pipeline creation to ingest data.

       You can change this setting later.

5. Click TEST CONNECTION. This button is enabled once you specify all the mandatory fields. Hevo’s underlying connectivity checker validates the connection settings you provide.

6. Click TEST & CONTINUE to proceed for setting up the Destination. This button is enabled once you specify all the mandatory fields.

Object and Query Mode Settings

Once you have specified the Source connection settings in Step 6 above, do one of the following:

• For Pipelines with Table or BinLog mode:

  1. On the Select Objects page, select the objects you want to replicate and click CONTINUE.

     

     Note: Each object represents a table in your database.

  2. On the Configure Objects page, specify the query mode you want to use for each selected object.

     

• For Pipelines with Custom SQL mode:

  1. On the Provide Query Settings page, enter the custom SQL query to fetch data from the Source.

  2. In the Query Mode drop-down, select the query mode, and click CONTINUE.

     

Data Replication

Note: The custom frequency must be set in hours as an integer value. For example, 1, 2, or 3 but not 1.5 or 1.75.

• Historical Data: In the first run of the Pipeline, Hevo ingests all available data for the selected objects from your Source database.

• Incremental Data: Once the historical load is complete, data is ingested as per the ingestion frequency.