You can define a subscription as an unbound subscription.
While regular subscriptions retrieve published data according to publication instances, unbound subscriptions ignore publication instances and retrieve the data according to the defined filter, regardless of when or in what batch the data was published.
Use this type of subscription when you want to receive the data according to a business-related logic and not according to publication batches.
When you define the topic from which the unbound subscription consumes data, you can define one or more filter accelerators. Filter accelerators are table columns that define how
Data Integration Hub
retrieves data based on business-related logic.
Data Integration Hub
indexes filter accelerator columns to accelerate data retrieval.
For example, an application publishes orders to
Data Integration Hub
when the orders are sent to the ordering system. The accounting system must receive the orders according to the business-date range, which is not necessarily according to the batches in which the orders are published. To deliver the orders according to the business-date range, perform the following steps:
In the topic to which the application publishes the orders, set the business-date column as a filter accelerator.
Create an unbound subscription that subscribes to the topic that publishes the orders and define a filter that is based on the business-date column.
The subscription consumes the orders according to the relevant business date, regardless of when and how they are published.