Hi there,
I'm getting this exception running a Storm topology on Windows.
D:\Stash\audit-refinery>*storm jar target\AuditApp-1.0-SNAPSHOT.jar
com.eze.exhaust.AuditTopology*
118 [main] INFO com.eze.exhaust.AuditTopology - Using file name
configuration.properties
121 [main] INFO
Hi.
I have a project I'm currently working on. The idea is to implement
"scikit-learn" into Storm and integrate it with HDFS.
I've already implemented "scikit-learn". But, currently I'm using a text
file to read and write. However, I need to use HDFS, but finding it hard to
integrate with HDFS.
I was intending to test the Flux and security on 0.10.0 release. Will test
backflow also along with this. Thanks Taylor.
But continuing on the original discussion, another two interesting things i
observed -
1. No. of ackers make a difference in fan-out and fan-in topologies.
2. Determining the
Hello!
I have an use case where we have to deploy many tpologies in a storm
cluster.
1.we would like to know if running these topologies in combination with
apache slider over yarn would bring us some benefits in terms of resource
consumption?
2. in such cases (running many topolgies aprox 60)
You should wire the bolts one after the other, and the first will emit the
tuple to the second only when it has to. Don't use sleep, that's probably
not correct anyways.
On Jan 31, 2016 11:22 PM, "sujitha chinnu"
wrote:
> hai.,
> My requirement is to first