Github user Parth-Brahmbhatt commented on a diff in the pull request:

    https://github.com/apache/storm/pull/414#discussion_r24459097
  
    --- Diff: 
storm-core/src/jvm/backtype/storm/serialization/ThriftSerializationDelegate.java
 ---
    @@ -0,0 +1,52 @@
    +/**
    + * Licensed to the Apache Software Foundation (ASF) under one
    + * or more contributor license agreements.  See the NOTICE file
    + * distributed with this work for additional information
    + * regarding copyright ownership.  The ASF licenses this file
    + * to you under the Apache License, Version 2.0 (the
    + * "License"); you may not use this file except in compliance
    + * with the License.  You may obtain a copy of the License at
    + *
    + * http://www.apache.org/licenses/LICENSE-2.0
    + *
    + * Unless required by applicable law or agreed to in writing, software
    + * distributed under the License is distributed on an "AS IS" BASIS,
    + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    + * See the License for the specific language governing permissions and
    + * limitations under the License.
    + */
    +package backtype.storm.serialization;
    +
    +import org.apache.thrift.TBase;
    +import org.apache.thrift.TDeserializer;
    +import org.apache.thrift.TException;
    +import org.apache.thrift.TSerializer;
    +
    +import java.util.Map;
    +
    +public class ThriftSerializationDelegate implements SerializationDelegate {
    --- End diff --
    
    @revans2 I am sorry I am not sure what you mean when you say "topology 
serialization moved out". StormTopology is a thrift structure so I think we can 
use thriftSerializationDelegate. The Spouts and Bolts have Component structures 
which are just serialized java bytes. Do you mean every place where we are just 
calling "get_serialized_java" on thrift instances should use java 
serialization? I think that makes sense and I can make that change.  Let me 
know if I misunderstood your comment.


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to