Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.10.0
Description
Current AbstractStreamOperator has at least couple of issues:
- it's using deprecated SetupableStreamOperator interface, instead of relaying on StreamOperatorFactory.
- it depends on OneInputStreamOperator and TwoInputStreamOperator interfaces, by providing indirectly implementation of methods like processLatencyMarker, processLatencyMarker1 and processLatencyMarker2
Both of those things makes AbstractStreamOperator an unsuitable base implementation for MultipleInputStreamOperator. We should provide a new base class (or hierarchy of base classes), without those two limitations.
CC aljoscha
Attachments
Issue Links
- links to