Consider also whether you even *want* to pass large objects through your
tuples. If this will cause many copies of the object with no modification
or reference, you might be much better off leaving your object in a static
cache and simply passing around an ID. There are many heuristics for
managi
Yep. That's what I figured. Thanks.
On Sunday, January 12, 2014, Nathan Leung wrote:
> Muliti lang interface uses json which is a text format. Given an earlier
> email (
> http://mail-archives.apache.org/mod_mbox/storm-user/201401.mbox/%3CCAEN10JreBSFO-=xhNjbn9r+5+F+G=az8rw58qdo8x32gd-x...@mail.g
Muliti lang interface uses json which is a text format. Given an earlier
email (
http://mail-archives.apache.org/mod_mbox/storm-user/201401.mbox/%3CCAEN10JreBSFO-=xhNjbn9r+5+F+G=az8rw58qdo8x32gd-x...@mail.gmail.com%3E)
the object appears to be serialized to json using toString which for byte
array
I am using 0.9. What I think is the issue is that storm.py is having
problems when deserializing a byte array. When I encode as base64 binary
string I have no problems and it deserializes fine. Of course I would like
to avoid this extra overhead if possible. All my binary objects are
relatively sma
hi , Farchtchi,
which storm version are you using ?
IF the tuple is not serialized, then there is no need to use a JSON parser
to parse the received tuple. I guess so.
Regards
2014/1/11 Ruhollah Farchtchi
> Yes I read that in the docs. However when receiving the byte array in
> storm.py it th
Yes I read that in the docs. However when receiving the byte array in
storm.py it throws a json error when trying to parse the tuples. I didn't
have time to look into it further as I am new to storm and python.
On Saturday, January 11, 2014, 李家宏 wrote:
> There is no need to serialize binary data,
There is no need to serialize binary data, just send it as it.
As by defalut storm-0.9.0 use kryo serializer to serialize tuple values, I
guess we can skip this serialization step.
Regards
2014/1/10 Jon Logan
> You're going to run into issues if you have large tuples, because they are
> buffe
You're going to run into issues if you have large tuples, because they are
buffered in memory. I would suggest moving it to an exterior channel, like
Redis, etc, and only passing meta-data through Storm.
Your other solution is to use quirky things like reflection to prevent your
application from r
I am using storm to process small (< 100k) image files. I don't have a
real-time requirement as yet, but my bottle neck is more in the image
processing than message passing between bolts. I am using the Clojure DSL
and the python bolt. Everything I've put together right now is very much a
prototype
I come up with this problem as well. I am considering using storm with real
time ip packet processing.
Regards,
Gvain
2014/1/10 Lochlainn Wilson
> Hi all,
>
> I am new to Storm and have been tasked with determining whether it is
> feasible for us to use Apache storm in my company. I have of c
Hi all,
I am new to Storm and have been tasked with determining whether it is
feasible for us to use Apache storm in my company. I have of course
configured the sample projects and have been poking around. A red flag is
raised with the "stream processing" style JSON parsing.
I am considering usin
11 matches
Mail list logo
