Huijun Wu

agree for the old jobs. the storm-api compatibility is one major motivation when heron was born, which is still a selling point at present. btw, besides storm api, propose to...

Adding versions might be too much.. Doubt if we have that many efforts to maintain each version Assume storm 2.x series share the same API, we can move to any...

`heron submit ... --config-property heron.classpath.instance= ..` This option is passed to heron-executor which launches heron-instance with the specified class path. For a general container, it needs two tar.gz: heron-core.tar.gz and...

If your topology is having "Class is not registered" error with Kryo, you could solve it by adding the following line into your topology source code: ``` Config config =...

Checked the code. https://github.com/apache/incubator-heron/blob/master/storm-compatibility/v0.10.2/src/java/org/apache/storm/Config.java#L456 and https://github.com/apache/incubator-heron/blob/master/storm-compatibility/v0.10.2/src/java/org/apache/storm/Config.java#L76 It looks like, it will generate some code .. this requires re-compiling

the master branch is on py3. the release process needs to catch up for pypi, docker hub etc. though

Curious the motivation to choose PEX. why not use the Bazel `py_binary`, which could make the building process easier?