[jira] [Comment Edited] (STORM-1842) Forward references in storm.thrift cause tooling issues

["Jungtaek Lim (JIRA)" <ji...@apache.org>]

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

Jungtaek Lim edited comment on STORM-1842 at 5/17/16 8:54 PM:
--------------------------------------------------------------

[~barrywhart] 
Here's custom build of Storm 1.0.2 SNAPSHOT + STORM-1842 patch.
http://people.apache.org/~kabhwan/storm-core-1.0.2-SNAPSHOT.jar

If it incurs other issues please let me know so that I just apply STORM-1842 with Storm 1.0.1 and rebuild.


was (Author: kabhwan):
[~barrywhart] 
Here's custom build of Storm 1.0.2 SNAPSHOT + STORM-1842 patch.
http://people.apache.org/~kabhwan/storm-core-1.0.2-SNAPSHOT.jar

If it incurs other issues please let me know that I just apply STORM-1842 with Storm 1.0.1 and rebuild.

> Forward references in storm.thrift cause tooling issues
> -------------------------------------------------------
>
>                 Key: STORM-1842
>                 URL: https://issues.apache.org/jira/browse/STORM-1842
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: storm-core
>    Affects Versions: 1.0.0
>            Reporter: Barry Hart
>            Assignee: Jungtaek Lim
>            Priority: Critical
>         Attachments: ttypes.py
>
>
> In recent versions of Storm (starting with version 1.0.0, I believe), storm.thrift uses several types before they are declared:
> * HBPulse
> * HBRecords
> * HBNodes
> These types are used in the definition of HBMessageData.
> This causes issues with downstream tools. For example, generating Python wrappers for the Storm Thrift types creates a module that will not import successfully.
> Would it be possible to reorder this code to define the types before using them? This appears to be a simple change.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)