Page Comparison

Snap executes MySQL bulk load.  This Snap uses the LOAD DATA INFILE statement internally to perform the bulk load action. The file is first copied to JCC node, then to MySQL server under tmp directory and finally to the target MySQL table. 

Table Creation

If the table does not exist when the Snap tries to do the load, and the Create table property is set, the table will be created with the columns and data types required to hold the values in the first input document. If you would like the table to be created with the same schema as a source table, you can connect the second output view of a Select Snap to the second input view of this Snap. The extra view in the Select and Bulk Load Snaps are used to pass metadata about the table, effectively allowing you to replicate a table from one database to another.
 

The table metadata document that is read in by the second input view contains a dump of the JDBC DatabaseMetaData class. The document can be manipulated to affect

the CREATE TABLE statement that is generated by this Snap. For example, to rename

the name column to full_name, you can use a Mapper (Data) Snap that sets the

path $.columns.name.COLUMN_

NAME to full_name.  The document contains the following fields:

• columns - Contains the result of the getColumns() method with each column as a separate field in the object. Changing

• the COLUMN_

• NAME value will change the name of the column in the created table. Note that if you change a column name, you do not need to change the name of the field in the row input documents. The Snap will automatically translate from the original name to the new name. For example, when changing

• from name to full_name,

• the name field in the input document will be put into the "full_name" column. You can also drop a column by setting

• the COLUMN_

• NAME value to null or the empty string.  The other fields of interest in the column definition are:

  • TYPE_

• • NAME - The type to use for the column.  If this type is not known to the database,

• • the DATA_

• • TYPE field will be used as a fallback.  If you want to explicitly set a type for a column, set

• • the DATA_

• • TYPE field.

  • _SL_

• • PRECISION - Contains the result of the getPrecision() method.  This field is used along with the _SL_

• • SCALE field for setting the precision and scale of

• • a DECIMAL or NUMERIC field.

  • _SL_

• • SCALE - Contains the result of the getScale() method.  This field is used along with the _SL_

• • PRECISION field for setting the precision and scale of

• • a DECIMAL or NUMERIC field.

• primaryKeyColumns - Contains the result of the getPrimaryKeys() method with each column as a separate field in the object.

• declaration - Contains the result of the getTables() method for this table. The values in this object are just informational at the moment.  The target table name is taken from the Snap property.

• importedKeys - Contains the foreign key information from the getImportedKeys() method. The

• generated CREATE TABLE statement will include FOREIGN KEY constraints based on the contents of this object. Note that you will need to change

• the PKTABLE_

• NAME value if you changed the name of the referenced table when replicating it.

• indexInfo - Contains the result of the getIndexInfo() method for this table with each index as a separated field in the object.  Any UNIQUE indexes in here will be included in

• the CREATE TABLE statement generated by this Snap.

This Snap uses account references created on the Accounts page of SnapLogic

Manager to handle access to this endpoint. See MySQL Account

 for information on setting up this type of account.

The database schema name. In case it is not defined, then the suggestion for the Table name will retrieve all tables names of all schemas. The property is suggestible and will retrieve available database schemas during suggest values.

Example: SYS
Default value: [None] 

Required. Table on which to execute the bulk load operation.

Example: people
Default value:  [None] 

The MySQL server uses the character set indicated by the character_set_database system variable to interpret the information in the inputs. If the contents of the inputs use a character set that differs from the default, it is recommended that you specify the character set of the inputs with this property. A character set of binary specifies "no conversion".

 Default: [None]