You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@storm.apache.org by HeartSaVioR <gi...@git.apache.org> on 2016/12/28 22:50:15 UTC

[GitHub] storm issue #1844: STORM-2265: Incorrectly Serialized JSON in TransactionalS...

Github user HeartSaVioR commented on the issue:

    https://github.com/apache/storm/pull/1844
  
    @hmcl 
    I filed STORM-2264, and thought about this approach before.
    
    This approach makes GlobalPartitionInformation serialized well, but the type is lost when deserializing. Deserialized object is not GlobalPartitionInformation. 
    I haven't deeply look into storm-kafka Trident implementation so hard to guess how this affects.
    
    If we're not sure, just replacing JSONValue.parseWithException to JSONValue.parse only from TransactionalState rolls back the problem. It's just hiding an long ago issue again so need to find out clearer way but given that it is critical, we may need quick fix first.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---