Github user tony810430 commented on the issue:
https://github.com/apache/flink/pull/3474
Hi, @StephanEwen
I mean although all subclasses will be forced to call the one-argument
constructor, it doesn't force all subclasses need to have the one-argument
constructor. It seems not intuition to add an one-argument constructor if there
is another requirement for a new subclass.
However, tests might help us find out this mistake. Maybe it is not a
problem.
One more question, `StreamTask` needs `setInitialState()` to initialize
itself as well. Will that be okey to make the subclass of both
`AbstractInvokable` and `StatefulTask` to have two-arguments constructor and
remove `setInitialState()` method?
If it works fine for you and @tillrohrmann, I have no more question.
Please help me create a JIRA task for (1, 2). I will pend this PR until I
have finished that task and redo it as (3). Thank you.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
