Closed ddebrunner closed 8 years ago
This is related to #68
Why extend Topology
and TStream
instead of just defining a new connector?
Good question.
My first reaction is that publish/subscribe is inherently part of the provider/runtime, therefore not a connector.
But a connector may make more sense, I'll think about it for a while.
Pull request #98 implements pub/sub using the connector style suggested by @dlaboss
Allow a running job to publish tuples that can be subscribed to by other running jobs.
Method in TStream:
<U super/extends T> TSink<T> publish(String topic, Class<U> streamType)
Method in Topology