I believe it's because different types of sinks can get plugged in depending on how the operators are deployed. If the operator and its downstream operator are in same container it is a queue otherwise it is a publisher to buffer server that is serializing the data generically independent of the data type.
Thanks > On Jun 29, 2016, at 1:41 PM, Siyuan Hua <[email protected]> wrote: > > The setSink method on OutputPort<T> takes Sink<Object> > > But the getSink method on InputPort<T> returns a Sink<T> > > Is there a reason for this asymmetric API ? > > Regards, > Siyuan
