Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1136
@vesense
Sorry to reach out too late. Some comments for me:
1. We might want to include this to multilang (like multilang-serializer)
module so that it doesn't affect dependency if users don't use multilang
feature. But I'm also OK to have this to core if we are OK to just shade
msgpack.
2. As @dan-blanchard stated we may want to have stable implementation of
serializer if possible.
3. I totally agree with @dan-blanchard that changing default behavior
should be avoided unless releasing major version.
4. It requires users to implement custom multi-lang logic to apply
deserialization. IMO, I think it makes issue more complicated. We could provide
implementation by default, but it will force user to have dependency at all,
and more bad thing is that we need to address this at least three languages.
Personally I feel that we're stuck on having less-maintaining and
non-library-dependent default implementations. I can take care of python / ruby
implementation though I'm not expert on these, but have no idea on nodejs.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
