-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Storm 1.0.3 #90
Comments
Are you using the 1.0.1.0.3 version from here? That one should work, unless I built it incorrectly. If necessary, you can build from source by installing your desired Storm version, then running Let me know if the pypi version is wrong, I can build and upload a corrected one. The build process is still slightly manual, unfortunately, for example, the jvmpetrel/pom.xml file has to be updated for each new Storm version. There may be a better way to do it; I am not a Maven expert. |
Instructions on building from source: https://github.com/AirSage/Petrel#installing-petrel-from-source |
https://pypi.python.org/simple/petrel/
Only petrel-1.0.2.0.3-py3.5.egg is available for python 3.5 |
Just in case the following is the message I get:
|
I made some mistakes uploading. Apparently even though the Python code is compatible with both 2.7 and 3.5, I need to explicitly upload a wheel file for Python 3.5. I'll try and do this in the next day or two. |
I uploaded a new build, petrel-1.0.3.0.3-py3-none-any.whl. Uploading the corresponding Python 2.7 wheel next. Have not yet done a test download/install. |
Download from pypi in Python 3.5 looks good:
|
Getting an error when the wordcount topology starts up:
|
The problem occurs with both Python 2.7 and 3.5 on Storm 1.0.3. I do not see the same issue with Storm 1.0.1. I will try Storm 1.0.2. |
I uploaded 2.7 and 3.5 wheel files to pypi and verified that Storm 1.0.2 works correctly with Python 3.5.3. The error that is occurring in 1.0.3 sounds like a Storm issue that other people have reported at various times. (Try doing a web search for "stormconf.ser does not exist".) It seems likely to be a Storm bug or a problem with my environment. Can you try Storm 1.0.3 with Petrel 1.0.3.0.2 and see if it works for you? |
hi Barry - thank you! I will test tomorrow morning and let you know results
…On Tue, Apr 18, 2017 at 5:12 PM, Barry Hart ***@***.***> wrote:
I uploaded 2.7 and 3.5 wheel files to pypi and verified that Storm 1.0.2
works correctly with Python 3.5.3. The error that is occurring in 1.0.3
sounds like a Storm issue that other people have reported at various times.
(Try doing a web search for "stormconf.ser does not exist".)
It seems likely to be a Storm bug or a problem with my environment. Can
you try Storm 1.0.3 with Petrel 1.0.3.0.2 and see if it works for you?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#90 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABqqxckeOoXj9RnhT1WUw8FrYVqfwXXiks5rxVFjgaJpZM4M-GKv>
.
--
*Simplicity - Beauty of the Person. *
Clickbrand.com - making tomorrow today
|
this is the error I got once topology is submitted
And then I'm getting tons of *.log files representing bolts and spouts tasks around 300 bytes long with similar content
setup.sh
requirements/production.txt:
switched back petrel-1.0.2.0.3 installed with easy_install and now topology works successfully, snapshot of my virtualenv log after install |
I found an issue which I think explains this error:
Petrel was still trying to use I made that change and pushed a new version to PyPI: 1.0.3.0.3.post1. Because of the
I have created a PR so you can see the changes related to adding 1.0.3 support. Please take a look; in case of issues, this may help you figure out any remaining problems more quickly. |
hi Barry, thank you for your work!
|
@LW-YUNKAI: I am no longer an AirSage employee, and AirSage asked me to turn over control of the AirSage GitHub organization to them. As a result, I am no longer supporting Petrel. I regret I cannot help you. |
oh that's really a bad news. That means that petrel is officially DEAD? Is
it possible to take over support and maintenance of Petrel? Or intellectual
property is owned by AirSage completely and nothing we can do?
…On Wed, Oct 25, 2017 at 11:58 AM, Barry Hart ***@***.***> wrote:
@LW-YUNKAI <https://github.com/lw-yunkai>: I am no longer an AirSage
employee, and AirSage asked me to turn over control of the AirSage GitHub
organization to them. As a result, I am no longer supporting Petrel. I
regret I cannot help you.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#90 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABqqxdOIY9DV1sYI7QAZtGlXOoz3U6enks5sv4TxgaJpZM4M-GKv>
.
--
*Simplicity - Beauty of the Person. *
Clickbrand.com - making tomorrow today
|
@barrywhart It is a pity! I hope that STORM could have better support for python in the future! Thank you anyway! |
hi Barry,
Petrel complains that Apache storm version is not equal to 1.0.2 when I submit into storm cluster v 1.0.3 (due to supplied Jar file?)
../../jvmpetrel/target/storm-petrel-*-SNAPSHOT.jar
Where can I get jar file for 1.0.3?
Thanks,
Dmitry
The text was updated successfully, but these errors were encountered: