Fabric Transaction Management
Fabric has a built-in Transaction management mechanism that handles a transaction during data processing. Transactions are handled differently in different data processing modules.
Sync Process
During the synchronization of an LU Instance (LUI), the data is retrieved from the source systems and loaded into the Fabric database. The LU tables population and enrichment functions are both executed in a Sync process.
The Sync process is managed as a single transaction that starts at the beginning of the Sync process and finishes at its end. If the Sync is completed successfully, the data is committed to the Fabric database. However, if an error occurs at any point during the Sync process, the transaction is rolled back.
When a Sync process is invoked by a Web Service or a User Job, the transaction can be managed by the calling process. For example, you can start a transaction in a Web Service, get an LUI, perform additional updates on the Fabric database and then commit. In this scenario, all the changes including those of the Sync will be committed.
Click for more information about Sync LUI.
Broadway Flows
Broadway flows can be split into two categories: an LU table population based on a Broadway flow and a regular Broadway flow executed not as part of a population. The transaction is managed differently in each of these categories:
- Broadway population flows are executed during the Sync process and therefore the management of a transaction in a flow is done as part of the overall Sync process transaction. There is no separate transaction for a Broadway flow in this case.
- When a Broadway flow is executed not as part of a population, Broadway must manage this transaction.
Note that when a Broadway flow is invoked by a Web Service or a User Job, the transaction can also be managed by the calling process, as explained above in reference to the Sync process.
Click for more information about Transactions in Broadway flows.
Fabric Transactions
Fabric enables updating a specific LU table for the given LUI (Instance ID) in the Fabric database or an entry in the Reference table instead of synchronizing the entire Instance ID or the Reference table from the source. This functionality is used when:
- Fabric is the master of the specific data.
- Fabric needs to be updated if the feeds from the source didn't arrive or the data is not in-sync for some reason.
Click for more information about Fabric Transactions.
Fabric Transaction Management
Fabric has a built-in Transaction management mechanism that handles a transaction during data processing. Transactions are handled differently in different data processing modules.
Sync Process
During the synchronization of an LU Instance (LUI), the data is retrieved from the source systems and loaded into the Fabric database. The LU tables population and enrichment functions are both executed in a Sync process.
The Sync process is managed as a single transaction that starts at the beginning of the Sync process and finishes at its end. If the Sync is completed successfully, the data is committed to the Fabric database. However, if an error occurs at any point during the Sync process, the transaction is rolled back.
When a Sync process is invoked by a Web Service or a User Job, the transaction can be managed by the calling process. For example, you can start a transaction in a Web Service, get an LUI, perform additional updates on the Fabric database and then commit. In this scenario, all the changes including those of the Sync will be committed.
Click for more information about Sync LUI.
Broadway Flows
Broadway flows can be split into two categories: an LU table population based on a Broadway flow and a regular Broadway flow executed not as part of a population. The transaction is managed differently in each of these categories:
- Broadway population flows are executed during the Sync process and therefore the management of a transaction in a flow is done as part of the overall Sync process transaction. There is no separate transaction for a Broadway flow in this case.
- When a Broadway flow is executed not as part of a population, Broadway must manage this transaction.
Note that when a Broadway flow is invoked by a Web Service or a User Job, the transaction can also be managed by the calling process, as explained above in reference to the Sync process.
Click for more information about Transactions in Broadway flows.
Fabric Transactions
Fabric enables updating a specific LU table for the given LUI (Instance ID) in the Fabric database or an entry in the Reference table instead of synchronizing the entire Instance ID or the Reference table from the source. This functionality is used when:
- Fabric is the master of the specific data.
- Fabric needs to be updated if the feeds from the source didn't arrive or the data is not in-sync for some reason.
Click for more information about Fabric Transactions.
