Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Bolo.

Table of Contents

Search

  1. Introducing Mass Ingestion
  2. Getting Started with Mass Ingestion
  3. Connectors and Connections
  4. Mass Ingestion Applications
  5. Mass Ingestion Databases
  6. Mass Ingestion Files
  7. Mass Ingestion Streaming
  8. Monitoring Mass Ingestion Jobs
  9. Asset Management
  10. Troubleshooting

Mass Ingestion

Mass Ingestion

MySQL sources

MySQL sources

To use MySQL sources in database ingestion tasks, first prepare the source database and review the usage considerations.

Source preparation

  • To deploy and run a
    database ingestion
    task that includes a MySQL source, the source connection must specify a database user who has the privileges that are required to perform an initial load operation. Use the following SQL statements to grant these privileges to the user:
    GRANT SELECT ON
    database_name
    .* TO '
    user_name
    '@'%'; GRANT SELECT TABLES ON
    database_name
    .* TO '
    user_name
    '@'%';
  • If you use Amazon Relational Database Service (RDS) for MySQL source, you must download the MySQL Native Driver and copy it to the following directory:
    Secure_Agent_installation_directory
    /ext/connectors/thirdparty/com.mysql
    Database ingestion jobs can then use the driver to connect to the RDS for MySQL source.

Usage considerations

  • Mass Ingestion Databases
    supports RDS for MySQL sources for initial load jobs.
  • Mass Ingestion Databases
    does not support the following MySQL data types:
    • BLOB
    • GEOMETRY
    • GEOMETRYCOLLECTION
    • JSON
    • LINESTRING
    • LONGBLOB
    • LONGTEXT
    • MEDIUMBLOB
    • MEDIUMTEXT
    • MULTILINESTRING
    • MULTIPOINT
    • MULTIPOLYGON
    • POINT
    • POLYGON
    • TEXT
    • TINYBLOB
    • TINYTEXT
    Database ingestion
    jobs propagate nulls for columns that have these data types.
    For information about the default mappings of supported data types, see the Data Type Mappings Reference.

0 COMMENTS

We’d like to hear from you!