airflow.providers.mysql.transfers.vertica_to_mysql

Module Contents

Classes

VerticaToMySqlOperator

Moves data from Vertica to MySQL.
class airflow.providers.mysql.transfers.vertica_to_mysql.VerticaToMySqlOperator(sql, mysql_table, vertica_conn_id='vertica_default', mysql_conn_id='mysql_default', mysql_preoperator=None, mysql_postoperator=None, bulk_load=False, *args, **kwargs)[source]

Bases: airflow.models.BaseOperator

Moves data from Vertica to MySQL.

Parameters

  • sql (str) – SQL query to execute against the Vertica database. (templated)

  • vertica_conn_id (str) – source Vertica connection

  • mysql_table (str) – target MySQL table, use dot notation to target a specific database. (templated)

  • mysql_conn_id (str) – Reference to mysql connection id.

  • mysql_preoperator (str | None) – sql statement to run against MySQL prior to import, typically use to truncate of delete in place of the data coming in, allowing the task to be idempotent (running the task twice won’t double load data). (templated)

  • mysql_postoperator (str | None) – sql statement to run against MySQL after the import, typically used to move data from staging to production and issue cleanup commands. (templated)

  • bulk_load (bool) – flag to use bulk_load option. This loads MySQL directly from a tab-delimited text file using the LOAD DATA LOCAL INFILE command. The MySQL server must support loading local files via this command (it is disabled by default).

template_fields :Sequence[str] = ['sql', 'mysql_table', 'mysql_preoperator', 'mysql_postoperator'][source]
template_ext :Sequence[str] = ['.sql'][source]
template_fields_renderers[source]
ui_color = #a0e08c[source]
execute(context)[source]

This is the main method to derive when creating an operator. Context is the same dictionary used as when rendering jinja templates.

Refer to get_template_context for more context.

Was this entry helpful?