GoConqr has a new look! Let us know what you think.

Mind map

1_JOINER Transformation - Transaction Scope Property

v_krejci English

Map content

1_JOINER Transformation - Transaction Scope Property

  1. Transaction Scope Property - apply transformation logic to all data in transaction (Transaction), all incoming data (All Input), or one row of data at a time (Row)

    • Drop or preserve transaction bounderies based on mapping configuration and transformation scope.
      • Preserve Transaction Boundaries - join two branches of the same source pipeline or join two sources and you want to preserve transaction boundaries for the detail source
      • Drop Transaction Boundaries - join two sources or two branches and you want to drop transaction boundaries. Use All Input scope to apply to all incoming data and drop boundaries for both pipelines.
      • Summary
        • Row - Unsorted - Preserve Transaction boundaries in the detail pipeline
        • Row - Sorted - Session fails
        • Transaction - Sorted - Preserves when master nad detail from the same transaction generator; otherwise it fails
        • Transaction - Unsorted - session Fails
        • All Input - Sorted, Unsorted - Drops transaction boundaries
  2. ACTIVE

Information

Description
Mind Map on 1_JOINER Transformation - Transaction Scope Property, created by v_krejci on 03/11/2015.
Created by
v_krejci
Views
1
History
  • Created by v_krejci · Nov 3, 2015
  • Copied by v_krejci · Nov 3, 2015
Rating

Feedback

What is it about?

What do you think of the new look?

How do you like it?