[
https://issues.apache.org/jira/browse/STORM-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barry Hart updated STORM-1842:
------------------------------
Priority: Critical (was: Major)
Description:
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.
was:
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.
> 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
> Priority: Critical
>
> 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)
