Local Data Exchange Component

The Local Data Exchange component allows deployments operating on the same runtime to pass data back and forth between them. Data passed into a Local Data Exchange component in one deployed blueprint is returned from the corresponding Local Data Exchange component in the other deployed blueprint. The data flow is bidirectional allowing data to flow in both directions. 

If the Data Governance is enabled on the deployments, then the deployments that are communicating using the Remote Data Exchange component must be using the same DGS Context. If they aren't, the components will fail to connect and errors will be reported in the deployment audit logs. To set the DGS Context, add a blueprint setting called dgs.context  to each of the blueprints and set them all to the same unique value. Alternatively, for programmatically deployed blueprints, you can specify the DGS Context setting as a setting override during deployment of the blueprints.

If multiple independent channels of data need to be passed through this communication channel, it is recommended that a Multiplexer and Demultiplexer be placed in front of the Local Data Exchange components so that the streams can be cleanly aggregated and divided on either side.

Data Governance

If Data Governance is enabled, data items received by the component from the partner pipeline will be marked as received. If the data item's type is not recognized, the SerializedObjectData item will be recorded as having been derived from the original data item. 

Furthermore, deployments that are communicating using the Remote Data Exchange component must be using the same DGS Context. To set the DGS Context, add a blueprint setting called dgs.context   to each of the blueprints and set them all to the same unique value. Alternatively, for programmatically deployed blueprints, you can specify the DGS Context setting as a setting override during deployment of the blueprints.

Input Channels

data — Accepts a PipelineData object and transfers it to the partner component.

Output Channels

data — Returns any PipelineData object that it receives from its partner component. If the received item's data type is not recognized, returns a SerializedObjectData object containing the serialized form of the original item. If the component receives a SerializedObjectData object from the partner system and it recognizes its data type, it will reconstitute the original data item and return it.

Parameters

connectionID — The unique ID shared by the two components in the data exchange that allows them to locate each other and exchange data.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us