Data Source - MySQL (Aurora)
  • 07 Dec 2022
  • Dark
    Light
  • PDF

Data Source - MySQL (Aurora)

  • Dark
    Light
  • PDF

Article Summary

Note

This is a machine-translated version of the original Japanese article.
Please understand that some of the information contained on this page may be inaccurate.

summary

This is a help page for setting up data transfer from MySQL (Aurora).

Unlike normal MySQL transfer, the transfer is performed by outputting a temporary CSV file from Aurora to S3 and reading the CSV file.
Compared to the normal MySQL transfer method, it is possible to transfer large amounts of data while reducing the load on Aurora.
Please note that there is a specification that the column name of the transferred table is not inherited as the table name after the transfer.

constraint

  • Nothing in particular

Setting items

STEP1 Basic settings

Itemnamerequireddefault
valuecontent
Aurora MySQL connection informationYes-From the connection information registered in advance, select the one that has the necessary permissions for this transfer setting.
databaseYes-Specify the name of the database that contains the transferred MySQL data.
queryYes-Enter SQL to retrieve the transferred data from MySQL.
Do not include a ";" at the end of the query.
You can also set custom variables and embed them in your query.
S3 bucket nameYes-Specify the S3 bucket name to temporarily output data.

STEP2 Advanced settings

Item namedefault valuedetails
Skip query execution when transferring,
Start importing from a located S3 file
Do not skipSelect Skip to allow execution from the S3 file ingestion phase by skipping the query if the job fails after the Aurora query completes.
Socket timeout (seconds)1800You can set the maximum timeout period during transfer.
If the job execution time exceeds the time specified in this setting, the execution job stops.

supplement


Was this article helpful?