It sounds like you want a generic BI tool built on top of storm. I don't know
of any. Internally at Yahoo we use storm for BI in a number of different
custom built ways, but nothing that generic, or that is likely to be released
as open source.
- Bobby
On Tuesday, June 21, 2016 1:45 AM, Jungtaek Lim <[email protected]> wrote:
There're several ways of doing this.
- Relying on external storage is the easiest and standard way to do it. If
you consider about latency you can add cache layer too.
- From Storm 1.0.0 you can use Distributed Cache API to store/update/read
your keyword file. Please refer
http://storm.apache.org/releases/1.0.1/distcache-blobstore.html for more
details.
Hope this helps.
Thanks,
Jungtaek Lim (HeartSaVioR)
2016년 6월 21일 (화) 오후 3:03, Erik Weathers <[email protected]>님이
작성:
> You'll definitely need to explain more about what you *mean* by automatic
> vs. manual. Storm is just the framework that is running your code, this
> *sounds* like a problem in your own code.
>
> On Mon, Jun 20, 2016 at 10:22 PM, Rahul mahamna <[email protected]> wrote:
>
> > Hi
> > I am working on apache storm to analyse real time tweets and other stuff.
> > I am having a problem in making it automatic.
> > I am able to perform operation on real time tweets manually using storm
> > but i am looking for something where i can make it automatic in storm
> > itself. Whenever i am filtering a query using a particular keyword i have
> > to make jar again and again to the right tweet. So if i will make it
> > automatic then i have to make jar again and again for all the keywords
> > which will take time and consume my base memory. So can you suggest me an
> > option where i can directly insert my keyword to the same jar again and
> > again to get real time tweets in no time. Or if you have any other option
> > then please suggest me. Please reply
> >
> > thank you
> > --
> >
> >
> > IMPORTANT: This message may contain privileged and confidential
> information
> > that is the property of the intended recipient. If you are not the
> intended
> > recipient, you should not disclose or use the information contained in
> > it. If you have received this email in error, please notify us
> immediately
> > by return email and delete the document. Copying or disseminating any of
> > this message is prohibited. Any views expressed in this message are those
> > of the individual sender and may not necessarily reflect the views of
> > Appster.com.au <http://appster.com.au/> unless indicated otherwise.
> Before
> > opening or using attachments check them for viruses and defects.
> >
>
