Configure Destination Database

You can configure SingleStore databases as a destination. To configure the destination database, navigate to Dashboard > Destination, and then select the gear icon.

1. In the Destination Database dialog, select SingleStore from the Destination Database list.

2. In the SingleStore tab, enter the following configuration details:

   1. Host Name: Enter the IP address or hostname of the database server.

   2. Port: Enter the port number on which the database server is listening (default port for SingleStore is 3306).

   3. User ID: Enter a valid SingleStore user ID to be used with Ingest.

   4. Password: Enter the password for the SingleStore user.

      Note: Passwords are encrypted within Ingest.

   5. JDBC Options (Optional): JDBC options are optional and can be used to extend the JDBC URL for accessing the database.

3. Select the Advanced Options tab. Enter the following configuration details:

   1. Max Updates (Default maximum update is 4): Enter a number that controls when Flow consolidates multiple changes to the same record. When loading data, if the number of sequential changes to the same record exceeds twice this value, Flow groups the changes by primary key before applying them to the destination. Enter -1 to disable consolidation.

   2. Load Threads: Enter the number of parallel loading threads that Flow uses for the destination. Increase this value to allow more concurrent load activity, depending on the capacity of your host and SingleStore deployment.

   3. Add Database Prefix: Enter a prefix to add to the destination schema names. For example, if the prefix is prod and the source table is mydb:sales.customers, the destination becomes prod_mydb_sales.customers. Leave blank to use the original schema names.

   4. Truncate table instead of drop: Enable this to truncate existing destination tables instead of dropping and recreating them. Use this option when you want to reuse the destination table object while replacing its data.

   5. Database name and optional table name pattern: Controls how source tables are mapped to destination database and table names. Supports placeholders:

      %d - source database name

      %s - source schema name

      %t - source table name

      For more information and examples, refer to Destination Naming and Multi-Tenant Support.

   6. Ignore database name in schema: Enable this to exclude the source database name from destination table names. Use this when the source database name is not needed in the destination naming convention.

   7. Database for staging tables: Enter a schema or database name where Flow creates staging tables during the load process. Leave blank to create staging tables in the same location as the destination tables.

   8. Retain staging tables: Enable this to retain staging tables in the destination after loading completes. Enable this option when you want to inspect staging data for troubleshooting or validation.

   9. Sync Struct suppressed: Enable this to prevent Flow from recreating destination tables or applying schema changes when structure mismatches are detected, or when Sync Struct operations are run. When enabled, Flow ignores table structure differences and does not modify destination tables. This is disabled by default. For more information about Sync Struct, refer to Schema Evolution with Sync Struct.

   Refer to Appendix for more information.

4. Select Apply to confirm and save the details.

5. Select Test to verify the connectivity.

<dbname>.<destination_table_name>