there is no lock on genericPipeline.asyncEventListenerMap and care must be taken to avoid concurrency issues As of now, this method is called by xdcr_factory right after pipeline is constructed and async listeners are registered on parts This is the only time when genericPipeline.asyncEventListenerMap is initialized/modified, when concurrent access is not possible.

Used for testing only.

In certain scenarios, e.g., incorrect bucket password, a large number of parts may return error when starting.

temporary custom settings that need to be cleared after pipeline update.

GenericPipeline is the generic implementation of a data processing pipeline The assumption here is all the processing steps are self-connected, soonce incoming nozzle is open, it will propel the data through allprocessing steps.

The pipeline events mgr's job is to handle the exporting of events and also remember the user's preference on dismissing events.

the function constructs update settings for connectors of the pipeline.

the function constructs start settings for parts of the pipeline.

the function constructs update settings for parts of the pipeline.

the function constructs start settings for parts of the pipeline.