Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Works for Me
-
None
-
None
-
None
Description
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.