Does anyone have a good example program/instructions of using Python with
storm? I can’t seem to find anything concrete online.
Thanks,
Ashu Goel
https://github.com/apache/incubator-storm/tree/master/examples/storm-starter
The WordCountTopology contains an example python bolt.
Regards,
Dilpreet
On Thu, May 29, 2014 at 1:59 AM, Ashu Goel wrote:
> Does anyone have a good example program/instructions of using Python with
> storm? I can’t
Any examples where the entire infra is written in Python (including topology)?
or is that not possible
On May 28, 2014, at 1:33 PM, Dilpreet Singh
mailto:dilpreet...@gmail.com>> wrote:
https://github.com/apache/incubator-storm/tree/master/examples/storm-starter
The WordCountTopology contains an
Ashu, take a look this project: http://github.com/AirSage/Petrel
Write, submit, debug and monitor in python.
@ffranz
El 28/05/2014 22:49, Ashu Goel escribió:
Any examples where the entire infra is written in Python (including topology)?
or is that not possible
On May 28, 2014, at 1:33 PM, Dilp
Awesome! I’m looking more into using the storm.thrift to define a non-JVM DSL…
does anyone have any working examples of this? Python preferred but any example
will do. the wiki is a bit confusing...
On May 28, 2014, at 1:54 PM, FRANCISCO JESUS GOMEZ RODRIGUEZ
mailto:franciscojesus.gomezrodrig...
(the reason being is that we are still running Python 2.6 but Petrel is only
compatible with 2.7)
On May 29, 2014, at 2:48 PM, Ashu Goel
mailto:a...@shopkick.com>> wrote:
Awesome! I’m looking more into using the storm.thrift to define a non-JVM DSL…
does anyone have any working examples of this
We are building a new Storm and Python interop option that is called
streamparse:
https://github.com/Parsely/streamparse
It includes a heavily rewritten Storm interop library and a command line
tool, sparse, for managing local and remote Storm clusters. The idea is to
make Storm projects as easy
We had experimented with Storm/Python 6 months ago or so, but found the
JSON serialization/deserialization overhead was quite high, on the order of
several hundred usec per tuple every time it transitioned from java to
python or vice versa, limiting total throughput on a 12 core server to
around 25
For one thing, a recently accepted Storm pull request has made this
serialization pluggable and someone has already implemented a protobuf
variety. We plan to investigate alternative serialization options for
multilang once we get the other tooling out of the way.
For another, it is true the overh
Totally agree. I'd switch back to Python in a second if I could. Might be
worth taking a look at the pluggable serializer.
On Fri, May 30, 2014 at 5:14 PM, Andrew Montalenti
wrote:
> For one thing, a recently accepted Storm pull request has made this
> serialization pluggable and someone has al
Andrew,
>From what I understand streamparse still requires that the topologies be in
>Clojure… not entirely sure how this is different from what storm already
>provides. I was looking more for a DSL that we could use w/ Python 2.6 and be
>100% Python, but it looks like that is not available.
-
We decided to start with topology definitions in Clojure because a) that
ensures that the topologies can support 100% of Storm's Clojure DSL
out-of-the-box and b) that allows easy mixing of Python, Java, Clojure, and
even other multi-lang bolts. For example, we plan on producing example
topologies
12 matches
Mail list logo
