Search docs.molo17.com

    Vertica glyph screenshot Vertica agent

    Target Vertica

    Prerequisites

    To have Gluesync working on your Vertica instance you will need to have:

    • Valid user credentials with permission to read, and write to the target tables and respective database;

    Setup via Web UI

    • Hostname / IP Address: DNS record or IP Address of your database tenant;

    • Port: Optional, defaults to 5433;

    • Database name: Name of your target database;

    • Username: Username with read & write access to the target tables;

    • Password: Password belonging to the given username;

    Specific configuration

    This agent has no specific configuration properties.

    Updates with bulk operations during CDC

    When Use bulk operations during CDC (useBulkOperationsDuringCDC) is on for an entity, the agent does not apply an update as an UPDATE statement. It loads the change into a staging table, deletes the existing row from the target table and inserts the new version of it. With the option off, updates are applied as UPDATE statements.

    For the target table this has the following effects:

    • Columns that Gluesync does not write, such as a column with a default value, are set again as for a new row.

    Setup via Rest APIs

    Here following an example of calling the Core Hub’s Rest API via curl to setup the connection for this Agent.

    Connect the agent

    curl --location --request PUT 'http://core-hub-ip-address/pipelines/{pipelineId}/agents/{agentId}/config/credentials' \
    --header 'Content-Type: application/json' \
    --header 'Authorization: ••••••' \
    --data '{
            "hostCredentials": {
            "connectionName": "myAgentNickName",
            "host": "host-address",
            "port": 5433,
            "databaseName": "db_name",
            "username": "",
            "password": "",
            "maxConnectionsCount": 100,
            "enableTls": true,
            "certificatePath": "/myPath/cert.pem"
          }
    }'