[
https://issues.apache.org/jira/browse/STORM-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16258317#comment-16258317
]
Anton Alfred commented on STORM-2819:
-------------------------------------
The default Kryo implementation assumes that there would be (Plain Old Java
Objects) POJO for each serialized version of the object.
So if we have a customer document that has both basic detail, address, work
details, relationships to other customer details etc. POJO needs to be created
for each of these individual constructs. In a world where we do not know the
schema of the data this is not possible.
With JSON Parsers there are no POJOs to be created, the objects itself is a
dynamic object, unfortunately in the Java World we don't have the native
equivalent of the JavaScript world where the JSON itself is the object, in Java
gson like libraries needs to serialize to a JsonObject to make it available.
For now we are creating JsonObject serializing to a String in bolt, emit it to
the other bolt and then deserialize to String to JsonObject.
One should be able to natively pass the JsonObject just like Kryo for POJO
> Ability to natively support JSON serialization in topologies
> ------------------------------------------------------------
>
> Key: STORM-2819
> URL: https://issues.apache.org/jira/browse/STORM-2819
> Project: Apache Storm
> Issue Type: Improvement
> Components: storm-core
> Affects Versions: 1.0.2
> Environment: CentOS7, Docker
> Reporter: Anton Alfred
> Priority: Minor
> Labels: features
>
> Now that the world is moving towards NoSQL and most of the data is in JSON.
> Can a native JSON Serializer be implemented similar to support for Kryo.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
