Thanks Bobby. I will try that out.
On Thu, May 19, 2016 at 7:09 PM, Bobby Evans
wrote:
> It should be very simple to do with the distributed cache. Have them add
> the jar to the blob store and configure it to be downloaded with a link of
> their choosing. Then include that link in the topology
It should be very simple to do with the distributed cache. Have them add the
jar to the blob store and configure it to be downloaded with a link of their
choosing. Then include that link in the topology.classpath. The only thing to
be careful of is that if you upload a new version of the jar w
I have come across this requirement multiple times. For an end user,
creating a uber jar and submitting it directly works fine. But we have
systems which provide processing as a service. These systems take business
logic, completely agnostic of storm, from client in a jar. Service has its
own code
