[
https://issues.apache.org/jira/browse/STORM-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14316574#comment-14316574
]
Robert Joseph Evans commented on STORM-57:
------------------------------------------
This is still valid and acceptable. A ByteBuffer is not serializable, and
there is no built in kryo support for exporting it currently.
> Make Storm handle ByteBuffers as fields values natively
> -------------------------------------------------------
>
> Key: STORM-57
> URL: https://issues.apache.org/jira/browse/STORM-57
> Project: Apache Storm
> Issue Type: New Feature
> Reporter: James Xu
> Labels: Newbie
>
> https://github.com/nathanmarz/storm/issues/199
> Just need to make a ByteBuffer serializer and register it with Kryo as
> default.
> -------------------------
> brianmartin: I've written most of this but have run into a problem.
> ByteBuffer's are often HeapByteBuffer's, which is a private to java.nio.
> Therefore, it seems like even though ByteBuffer is registered, Kryo goes to
> the default serializer anyway because HeapByteBuffer is not registered.
> I'm not sure what a reasonable workaround for this would be.
> patch draft w/ test: https://gist.github.com/3094071
> --------------------------
> nathanmarz: Is there any sort of reflection trick you could use to get ahold
> of the HeapByteBuffer class and register it?
> --------------------------
> brianmartin: Ah, thanks for the tip.
> I've submitted a pull request for this. Apologies for not being able to
> attach the request to this issue (if that's possible).
> Let me know if any changes or contributor agreement are needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
