You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "David Willcox (JIRA)" <ji...@apache.org> on 2018/05/29 15:30:00 UTC

[jira] [Commented] (STORM-2839) Need ability to create Kryo serializer equivalent to Storm's

    [ https://issues.apache.org/jira/browse/STORM-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16493704#comment-16493704 ] 

David Willcox commented on STORM-2839:
--------------------------------------

I'd forgotten that I field this when I filed https://issues.apache.org/jira/browse/STORM-3088. That can be closed as duplicate, but there's a bit more detail and justification in that one that I'd suggest you check.

> Need ability to create Kryo serializer equivalent to Storm's
> ------------------------------------------------------------
>
>                 Key: STORM-2839
>                 URL: https://issues.apache.org/jira/browse/STORM-2839
>             Project: Apache Storm
>          Issue Type: Improvement
>          Components: storm-core
>            Reporter: David Willcox
>            Priority: Major
>
> What I _really_ want is to construct a Kryo serializer to serialize/deserialize a blob that's used down deep in a library. Said serializer doesn't have to be identical to Storm's, but I want it to have all of the same custom serializations registered that Storm uses.
> Ideally what I'd like is a public API to return a Kryo (de)serializer with the same configuration as Storm's.
> In practice, I _could_ configure a serializer using information in the Map passed to components' open/prepare, but I need that information down in the innards of the library. I can't depend on the caller pass down that down (since this is an internal detail of the library), and I'm not convinced that the library won't be invoked by Storm before components are even activated.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)