Apache Ignite Export
Field Description
- Export Type: Select Full Export/Incremental Export into Ignite.
- Target Database: The database type you want to export to (Ignite).
- JDBC Connection URL: The connection URL needed to connect to the target database.
- Username: Username of the target database (Not required for Ignite, you may enter dummy user).
- Password: Password of the target database (Not required for Ignite, you may enter dummy password).
- Target Schema: The schema in which you have the target table in Ignite.
- Target Table: Name of the target table.
- Export Columns: The selections of columns that must be exported to the target database. You must select at least one column. You can use the "Select all" and "Deselect All" buttons to make the selection faster.
- Natural Key Columns: Natural Key Columns are the columns that help determine a row uniquely.
- "_key" alias: "_key" alias column is used to uniquely determine row in Ignite cache if you have configured table key as one of the Java-defined datatypes like String, Integer, Float, Double, int etc.
- Max Number Of Connections: The maximum number of connections that you want to allow to write to the target database.
- Set Error Limit: If this checkbox is checked, you can specify an error limit.
- Error Limit: The limit on the numbers of rows that go to error table, before the job fails.
Feature Scope and Known Issues
- These datatypes in Hive are supported by the export feature: TINYINT, SMALLINT, INTEGER, BIGINT, TIMESTAMP, DATE, STRING, BOOLEAN, BINARY, CHAR, VARCHAR.
- These datatypes in Hive are not supported by the export feature: UNION, ARRAY, STRUCT, MAP.
- Currently, Incremental Export after the first export with zero rows in not supported. In such situation, please perform a full export once there is some data in the Hive table; post which, you can perform incremental exports.
Best Practices
- Use "_key" alias column only if you have defined Ignite table key as Java-defined datatypes like String, Integer, Float, Double, int etc.
- Natural Key should always be selected and unique for the table.
- Set an error limit to verify that the data has been transferred correctly.