Github user hmcl commented on the issue:
https://github.com/apache/storm/pull/1959
@revans2 yes, I knew what was the problem. However, it's very strong and
dangerous (as for backwards compatibility) to enforce base types (e.g
interfaces) to implement `java.io.Serializable`. We do that a lot across the
codebase, so I guess it is ok in this case as well.
I was not sure we wanted to make `Func` to extend `Serializable` as it
would automatically expose all the internals of all the implementations of this
interface. That's the reason I did the proposed fix. If we agree that it's ok
to have `Func` extend `Serializable`, I will do as you suggested. Let me know.
---
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.
---
