Andrew, Thanks for bringing the private conversation back to the dev@ list so everyone has more context.
That being said, I’d encourage the use of the public mailing lists as much as possible. Private conversations exclude the larger community from participating in potentially fruitful discussions. Don’t get me wrong, I applaud you doing the right thing in bringing this back to the community. I just wish it could have happened sooner. All good. We just do better next time. :) -Taylor > On Sep 26, 2018, at 5:58 PM, amontalenti <[email protected]> wrote: > > Github user amontalenti commented on the issue: > > https://github.com/apache/storm/pull/1136 > > Was chatting with @roshannaik and @dan-blanchard today, and this PR came > up. > > Someone on Storm team may benefit from taking a look at this as part of > the performance revisions being done for Storm 2.0. As mentioned in [#428 in > streamparse](https://github.com/Parsely/streamparse/issues/428#issuecomment-380135343) > -- the community project for running Python multi-lang topologies with Storm > -- getting this merged somewhere in the Storm codebase would open up the > possibility to switch serializer from Kryo & JSON to msgpack throughout, > which would speed up multi-lang use cases considerably. This PR includes a > pure Java implementation of a msgpack serializer, as well as pointers to the > right msgpack library in the Java community; it just needs to be reviewed, > tested, and merged. > > > ---
