A port of https://github.com/AbsaOSS/spline/tree/release/0.3.9/persistence/hdfs/src/main/scala/za/co/absa/spline/persistence/hdfs
HttpLineageDispatcher is responsible for sending the lineage data to spline gateway through producer API
KafkaLineageDispatcher is responsible for sending the lineage data to spline gateway through kafka
This trait deals with the captured lineage information.
This trait deals with the captured lineage information.
When the lineage data is ready the instance of this trait is called to publish the result.
Which implementation is used depends on the configuration.
See za.co.absa.spline.harvester.conf.SplineConfigurer#lineageDispatcher
If you are using default Spline configurer a custom lineage dispatcher can be registered via the configuration properties. First you define name and then class for that dispatcher same way as it's done in spline.default.properties for the default http dispatcher.
See: za.co.absa.spline.harvester.conf.StandardSplineConfigurationStack
When registering the class via a property (using the Default Spline Configurer) the class has to have a constructor with the following signature:
@throws[SplineInitializationException] def constr(conf: org.apache.commons.configuration.Configuration)
A port of https://github.com/AbsaOSS/spline/tree/release/0.3.9/persistence/hdfs/src/main/scala/za/co/absa/spline/persistence/hdfs
Note: This class is unstable, experimental, is mostly used for debugging, with no guarantee to work properly for every generic use case in a real production application.
It is NOT thread-safe, strictly synchronous assuming a predefined order of method calls:
send(plan)
and thensend(event)