it.agilelab.bigdata.wasp.core.eventengine.eventconsumers
MailingPipegraphModel
Related Doc:
package eventconsumers
it.agilelab.bigdata.wasp.core.eventengine.eventconsumers
MailingPipegraph is a System pipegraph which consumes Event objects.
In order to activate the event consumption, the user has to properly define the mailing-pipegraph configuration properties in the event-engine section .conf files. MailingPipegraph configuration is composed by a MailWriter definition and a list of ETL configuration objects. The user can generate an arbitrary number of event mailing flow by defining as many configuration objects.
The MailWriter configuration stores the information required to access the smtp-server with the given account.
For each described event mailing flow, it will be spawned a dedicated ETL. Event consumption ETLs are composed by: * A single source of Event objects from a Kafka topic * A set of rules which trigger the creation of an Event object.
+--------+ +--------+ +--------+ | Event | | Event | | Event | | Source | | Source | | Source | +---+----+ +---+-+--+ +--------+ | | |----------+ | | | | | +---v----+ +---v----+ +---v----+ +---v----+ | Event | | Event | | Event | | Event | |Consumer| |Consumer| |Consumer| |Consumer| | ETL | | ETL | | ETL | | ETL | +--------+ +--------+ +--------+ +--------+ | | | | | | | | | +-v--------v-+ | | | Mailer | | +----------- > Sink <-------------+ +------------+
Different ETLs can have the same source of data, but all ETLs will have the same Mailer Sink.
Update: MailingPipegraphModel read a isSystem flag from configuration which declares whether or not the Pipegraph should be automatically started when starting Wasp with the startSystemPipegraph option. The default value in case the isSystem keyword is not present is false