Cloud Integration Hub

Back Next

Topic structure properties

The

Topic Structure

area of topic page includes the following properties:

Create Table From

Add tables to the topic. The topic must contain at least one table.

You can use one or more of the following methods to add tables to the topic:

Create a table from a connection. Use this method when the structure of a table in the data domain that the topic represents exists in a connection object. You can use relational, flat file, JDBC_IC, JDBCV2, and Salesforce connections to create topic tables. The

Add Table From Connection

dialog box shows up to 200 tables. You can also search for an object from a connection.

Create a table from a flat file. Use this method when the structure of a table in the data domain that the topic represents exists in a flat file.

Create a table from a metadata file. Use this method when the structure of a table in the data domain that the topic represents exists in a JSON, XML, XLS, or XLSX file. For more information, see Using metadata files to create topic tables in a relational database.

Create a new table. Use this method to define the structure manually if the structure of the table does not exist in a compatible file.

Show

Lists the tables in the topic. You can select to show a specific table.

The list of topic tables shows the following properties for each table:

Table: Name of the topic table. A topic table name must begin with an alphabetic character or underscore and can contain only ASCII alphanumeric characters or underscores. The name must be unique in the
Cloud Integration Hub
repository.
The physical topic table name in the staging database might differ from the actual topic table name that you enter at the time of the topic table creation.
Column: Name of the table column.
The name must begin with an alphabetic character or underscore and can contain only alphanumeric characters or underscores.
Filter Accelerator: Indicates that the column will be used in subscription queries and requires performance-related handling by
Cloud Integration Hub
. Use this indicator with topics that you plan to use for unbound subscriptions.

When you use filter accelerators, consider the following guidelines:

Filter accelerators slow down the writing of publication data to the
Cloud Integration Hub
publication repository.
Filter accelerators have no impact on subscriptions that do not use filters.
In a hosted publication repository, to use a column as a filter accelerator, you must change the value of
Encrypted
to
No
for the column.
You cannot use a column with a TEXT data type as a filter accelerator.
Data Type: Select from the list of available data types. By default,
Cloud Integration Hub
reads the data as string.
Precision: Available for string, decimal, and text data types.
For a string data type, the maximum precision is 4,000 characters.

For a decimal data type, the maximum precision is 38 characters.

For a text data type, the maximum precision is 4,000,000 characters if the
Encrypted
option is not selected, and 100,000 characters if the
Encrypted
option is selected.
Scale: Enabled only for data types that support data scaling.
For a decimal data type, the maximum scale is 30 characters if you use a hosted publication repository, and 38 characters if you use a private publication repository.

For a DATE_TIME data type, the default scale is 0. For example, if you define a scale of 2 for a DATE_TIME of 2022-02-04 00:40:23.946,
Cloud Integration Hub
rounds the DATE_TIME to 2022-02-04 00:40:23.950.
Encrypted: Determines whether
Cloud Integration Hub
encrypts the column. Applies to a hosted publication repository.
Default is disabled.; You can choose to enable encryption for topic data except for columns with a DATE_TIME data type. This applies to a hosted publication repository. To use a column as a filter accelerator in your mappings, change the value of
Encrypted
to
No
for the column.
Required: You can specify a field in a relational topic table as Required. If you enable this option, ensure that the data is published to the required fields. If the published data doesn't meet the required mandatory fields criteria, the event fails.
Default is disabled.