Table exports for JDBC systems are now available

Announcements
1

Table exports for JDBC systems are now available

Datasets can now be exported to external JDBC systems using table exports in Data Connection. Table exports introduce a new user experience for configuring exports of tabular data through an intuitive interface, a rich export mode selection, and the ability to explore the target system to configure the export. Table exports will work with custom JDBC systems configured with both direct connection and agent runtimes.

Export modes

Table exports support six distinct export modes to accommodate your unique requirements:

  • Efficiently mirror dataset to external table (recommended): The external table will always match what you see in the Foundry dataset.
  • Full dataset without truncation: Always export a snapshot of the entire view of the Foundry dataset, without truncating the external table first.
  • Full dataset with truncation: Truncate (drop) the target table, then export a snapshot of the full current dataset view.
  • Export incrementally: Exports only unexported transactions from the current view without truncating the target table.
  • Export incrementally with truncation: Truncate (drop) the target table, then export only transactions from the current view that have not previously been exported.
  • Export incrementally and fail if not APPEND: Exports only unexported transactions from the current view, failing if there is a SNAPSHOT, UPDATE, or DELETE transaction (after the first run).

Learn more about the details of each export mode in our documentation.

tej1-1
tej1-11506×915 78 KB

Example of an export mode selection in Data Connection.

Explore target systems

For a dataset to be exported, its schema must match the schema of a table on the target system. To help you configure the correct table, a source explorer is available to navigate all schemas and tables available on the target source.

tej2-1
tej2-1790×540 74.3 KB

Example of a source exploration dialog.

Migrate from export tasks

The addition of table exports is intended to replace the usage of the now sunsetted export tasks to export tabular data, and every user of export tasks is encouraged to migrate to table exports. Learn more about the differences between Data Connection exports and export tasks, and learn how to migrate your workflows.

What’s next on the development roadmap?

Currently, table exports are only available for custom JDBC sources. We plan to expand support for more connector types in the near future.

2

Since the new table exports are less flexible than legacy export tasks could you please add more documentation how to use external transforms for JDBC sources, including examples of pre- and post-sql?
Those configuration options have been very convenient to trigger processing of the exported data in the target system.

2 Likes