Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

The transaction behaviour for the GCP Storage collection agent is described here.

Emits

The agent emits commands that change the state of the file currently processed.

Command

Description

Begin Batch

Emitted before the first part of each collected file is fed into a workflow.

End Batch

Emitted after the last part of each collected file has been fed into the system.

Retrieves

The agent retrieves commands from other agents and based on them generates a state change of the file currently processed.

Command

Description

Cancel Batch

If a Cancel Batch message is received, the agent sends the batch to Data Veracity.

Note!

If the Cancel Batch behaviour defined on the workflow level is configured to abort the workflow, the agent will never receive the last Cancel Batch message. In this situation, Data Veracity will not be involved, and the file will not be moved, but left at its current place.

Hint End Batch

If a Hint End Batch message is received, the collector splits the batch at the end of the current block processed (32 kB), If the block end occurs within a UDR, the batch will be split at the end of the preceding UDR.

After a batch split, the collector emits an End Batch message, followed by a Begin Batch message (provided that there is data in the subsequent block).

  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.