XXX: we should separate the connector and the flow state instead of mixing them together.

XXX: we should separate the connector and the flow state instead of mixing them together.

XXX: we should separate the connector and the flow state instead of mixing them together.

XXX: we should separate the connector and the flow state instead of mixing them together.

XXX: we should separate the connector and the flow state instead of mixing them together.

XXX: we should separate the connector and the flow state instead of mixing them together.

Special barrier message used for task completion signals over the data channel Allows synchronization with data messages flow.

Supported mode of operation If something is announced as true, it can be later turned off through the setParameters call But if something is announced as not supported (false), it can't be turned on.

XXX (AK, 6/2024): not sure if it logically belongs here or to another iface file.

Pass options to use to the connector.

Abstraction for the read plan.

TODO (AK, 6/2024): byte[] should be in Avro or Protobuf format (maybe subject to negotiation based on capabilities - like a preference list advertized by a connector).

Provided by the user and uniquely determines the flow.

General Connector Interface.

Signalling Connector Interface for use by Coordinator.

General coordinator interface.

Signalling coordinator interface for use by connectors.