You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@storm.apache.org by "Ramin Farajollah (BLOOMBERG/ 731 LEX)" <rf...@bloomberg.net> on 2018/03/27 13:45:07 UTC
Long command line
Hi,
when Storm runs, it sets up the command line with full path of all jars to be included in the classpath.
How can I simplify the command line by specifying directories and wildcard where the jars reside?
In doing that, does Storm care about the order of the jars in cp?
Re: Long command line
Posted by Erik Weathers <ew...@groupon.com>.
Tian & Faisal, unfortunately just emailing the list itself with
"UNSUBSCRIBE" has no effect. There is a protocol to subscribe to the list
that you must have followed, and there is a similar protocol to
unsubscribe. The process is documented here:
- *https://storm.apache.org/getting-help.html
<https://storm.apache.org/getting-help.html>*
For your quick reference, to unsubscribe you can just send an email to:
- user-unsubscribe@storm.apache.org
- Erik
On Mon, Apr 9, 2018 at 12:52 PM, Tian Guo <ti...@gmail.com> wrote:
> UNSUBSCRIBE
>
> On 9 April 2018 at 19:06, Faisal Waris <fa...@gmail.com> wrote:
>
>> UNSUBSCRIBE
>>
>> On Thu, Apr 5, 2018 at 2:05 PM, Bobby Evans <bo...@apache.org> wrote:
>>
>>> Sorry this is a late reply.
>>>
>>> There is no way to switch the classpath over to wildcards without
>>> changing the code in storm.py.
>>>
>>> In newer versions of storm that has been done. You can see
>>> https://issues.apache.org/jira/browse/STORM-2191 for more details about
>>> it.
>>>
>>> Thanks,
>>>
>>> Bobby
>>>
>>>
>>> On Tue, Mar 27, 2018 at 8:45 AM Ramin Farajollah (BLOOMBERG/ 731 LEX) <
>>> rfarajollah@bloomberg.net> wrote:
>>>
>>>> Hi,
>>>>
>>>> when Storm runs, it sets up the command line with full path of all jars
>>>> to be included in the classpath.
>>>>
>>>> How can I simplify the command line by specifying directories and
>>>> wildcard where the jars reside?
>>>> In doing that, does Storm care about the order of the jars in cp?
>>>>
>>>>
>>>>
>>
>
>
> --
> Best Regards,
> Tian Guo
>
Re: Long command line
Posted by Tian Guo <ti...@gmail.com>.
UNSUBSCRIBE
On 9 April 2018 at 19:06, Faisal Waris <fa...@gmail.com> wrote:
> UNSUBSCRIBE
>
> On Thu, Apr 5, 2018 at 2:05 PM, Bobby Evans <bo...@apache.org> wrote:
>
>> Sorry this is a late reply.
>>
>> There is no way to switch the classpath over to wildcards without
>> changing the code in storm.py.
>>
>> In newer versions of storm that has been done. You can see
>> https://issues.apache.org/jira/browse/STORM-2191 for more details about
>> it.
>>
>> Thanks,
>>
>> Bobby
>>
>>
>> On Tue, Mar 27, 2018 at 8:45 AM Ramin Farajollah (BLOOMBERG/ 731 LEX) <
>> rfarajollah@bloomberg.net> wrote:
>>
>>> Hi,
>>>
>>> when Storm runs, it sets up the command line with full path of all jars
>>> to be included in the classpath.
>>>
>>> How can I simplify the command line by specifying directories and
>>> wildcard where the jars reside?
>>> In doing that, does Storm care about the order of the jars in cp?
>>>
>>>
>>>
>
--
Best Regards,
Tian Guo
Re: Long command line
Posted by Faisal Waris <fa...@gmail.com>.
UNSUBSCRIBE
On Thu, Apr 5, 2018 at 2:05 PM, Bobby Evans <bo...@apache.org> wrote:
> Sorry this is a late reply.
>
> There is no way to switch the classpath over to wildcards without changing
> the code in storm.py.
>
> In newer versions of storm that has been done. You can see
> https://issues.apache.org/jira/browse/STORM-2191 for more details about
> it.
>
> Thanks,
>
> Bobby
>
>
> On Tue, Mar 27, 2018 at 8:45 AM Ramin Farajollah (BLOOMBERG/ 731 LEX) <
> rfarajollah@bloomberg.net> wrote:
>
>> Hi,
>>
>> when Storm runs, it sets up the command line with full path of all jars
>> to be included in the classpath.
>>
>> How can I simplify the command line by specifying directories and
>> wildcard where the jars reside?
>> In doing that, does Storm care about the order of the jars in cp?
>>
>>
>>
Re: Long command line
Posted by Erik Weathers <ew...@groupon.com>.
Mohamed, maybe you missed my earlier response to Tian & Faisal?
unfortunately just emailing the list itself with "UNSUBSCRIBE" has no
effect. There is a protocol to subscribe to the list that you must have
followed, and there is a similar protocol to unsubscribe. The process is
documented here:
- *https://storm.apache.org/getting-help.html
<https://storm.apache.org/getting-help.html>*
For your quick reference, to unsubscribe you can just send an email to:
- user-unsubscribe@storm.apache.org
- Erik
On Mon, Apr 9, 2018 at 2:22 PM, Mohamed AlTantawy <mo...@agolo.com> wrote:
> UNSUBSCRIBE
>
>
> Mohamed AlTantawy | CTO @Agolo <http://www.agolo.com>
> 917-865-4983 | LinkedIn <http://www.linkedin.com/in/altantawy> | Twitter
> <https://twitter.com/mhmdltntwy>
>
>
>
> On Mon, Apr 9, 2018 at 4:52 PM, Erik Weathers <ew...@groupon.com>
> wrote:
>
>> Thanks for responding Bobby.
>>
>> Ramin, my team has worked with some other Bloomberg engineers on the
>> Storm-on-Mesos project where we are particularly impacted by the long
>> classpaths of Storm. Are you using Storm-on-Mesos or regular Storm? We
>> have backported the change of STORM-2191 to Storm v1.0.6, and there is a
>> build I created manually in my GitHub fork of Storm:
>>
>> - https://github.com/erikdw/storm/releases/tag/v1.0.6-storm-mesos1
>>
>> This custom Storm build has been used to create the Storm-on-Mesos builds
>> for v1.0.6.
>>
>> If you're using v1.0.6 you can use that custom build directly, or you can
>> take the changes and port them to whichever Storm version you are using and
>> rebuild it.
>>
>> Thanks,
>>
>> - Erik
>>
>> On Thu, Apr 5, 2018 at 11:05 AM, Bobby Evans <bo...@apache.org> wrote:
>>
>>> Sorry this is a late reply.
>>>
>>> There is no way to switch the classpath over to wildcards without
>>> changing the code in storm.py.
>>>
>>> In newer versions of storm that has been done. You can see
>>> https://issues.apache.org/jira/browse/STORM-2191
>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_STORM-2D2191&d=DwMFaQ&c=LNdz7nrxyGFUIUTz2qIULQ&r=cPg4mUupZEtURFK34GyDCtRjHoUmKrI7oHRZqAh3hZY&m=WLOm6VPJkmQ40D2AN0W2qLgpsO_EMMUs1tPY-ZmYsxU&s=nIEeLQ791cIUCrbWmmplg7P1AgashM_PCr6M262i0q4&e=>
>>> for more details about it.
>>>
>>> Thanks,
>>>
>>> Bobby
>>>
>>>
>>> On Tue, Mar 27, 2018 at 8:45 AM Ramin Farajollah (BLOOMBERG/ 731 LEX) <
>>> rfarajollah@bloomberg.net> wrote:
>>>
>>>> Hi,
>>>>
>>>> when Storm runs, it sets up the command line with full path of all jars
>>>> to be included in the classpath.
>>>>
>>>> How can I simplify the command line by specifying directories and
>>>> wildcard where the jars reside?
>>>> In doing that, does Storm care about the order of the jars in cp?
>>>>
>>>>
>>>>
>>
>
Re: Long command line
Posted by Mohamed AlTantawy <mo...@agolo.com>.
UNSUBSCRIBE
Mohamed AlTantawy | CTO @Agolo <http://www.agolo.com>
917-865-4983 | LinkedIn <http://www.linkedin.com/in/altantawy> | Twitter
<https://twitter.com/mhmdltntwy>
On Mon, Apr 9, 2018 at 4:52 PM, Erik Weathers <ew...@groupon.com> wrote:
> Thanks for responding Bobby.
>
> Ramin, my team has worked with some other Bloomberg engineers on the
> Storm-on-Mesos project where we are particularly impacted by the long
> classpaths of Storm. Are you using Storm-on-Mesos or regular Storm? We
> have backported the change of STORM-2191 to Storm v1.0.6, and there is a
> build I created manually in my GitHub fork of Storm:
>
> - https://github.com/erikdw/storm/releases/tag/v1.0.6-storm-mesos1
>
> This custom Storm build has been used to create the Storm-on-Mesos builds
> for v1.0.6.
>
> If you're using v1.0.6 you can use that custom build directly, or you can
> take the changes and port them to whichever Storm version you are using and
> rebuild it.
>
> Thanks,
>
> - Erik
>
> On Thu, Apr 5, 2018 at 11:05 AM, Bobby Evans <bo...@apache.org> wrote:
>
>> Sorry this is a late reply.
>>
>> There is no way to switch the classpath over to wildcards without
>> changing the code in storm.py.
>>
>> In newer versions of storm that has been done. You can see
>> https://issues.apache.org/jira/browse/STORM-2191
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_STORM-2D2191&d=DwMFaQ&c=LNdz7nrxyGFUIUTz2qIULQ&r=cPg4mUupZEtURFK34GyDCtRjHoUmKrI7oHRZqAh3hZY&m=WLOm6VPJkmQ40D2AN0W2qLgpsO_EMMUs1tPY-ZmYsxU&s=nIEeLQ791cIUCrbWmmplg7P1AgashM_PCr6M262i0q4&e=>
>> for more details about it.
>>
>> Thanks,
>>
>> Bobby
>>
>>
>> On Tue, Mar 27, 2018 at 8:45 AM Ramin Farajollah (BLOOMBERG/ 731 LEX) <
>> rfarajollah@bloomberg.net> wrote:
>>
>>> Hi,
>>>
>>> when Storm runs, it sets up the command line with full path of all jars
>>> to be included in the classpath.
>>>
>>> How can I simplify the command line by specifying directories and
>>> wildcard where the jars reside?
>>> In doing that, does Storm care about the order of the jars in cp?
>>>
>>>
>>>
>
Re: Long command line
Posted by Erik Weathers <ew...@groupon.com>.
Thanks for responding Bobby.
Ramin, my team has worked with some other Bloomberg engineers on the
Storm-on-Mesos project where we are particularly impacted by the long
classpaths of Storm. Are you using Storm-on-Mesos or regular Storm? We
have backported the change of STORM-2191 to Storm v1.0.6, and there is a
build I created manually in my GitHub fork of Storm:
- https://github.com/erikdw/storm/releases/tag/v1.0.6-storm-mesos1
This custom Storm build has been used to create the Storm-on-Mesos builds
for v1.0.6.
If you're using v1.0.6 you can use that custom build directly, or you can
take the changes and port them to whichever Storm version you are using and
rebuild it.
Thanks,
- Erik
On Thu, Apr 5, 2018 at 11:05 AM, Bobby Evans <bo...@apache.org> wrote:
> Sorry this is a late reply.
>
> There is no way to switch the classpath over to wildcards without changing
> the code in storm.py.
>
> In newer versions of storm that has been done. You can see
> https://issues.apache.org/jira/browse/STORM-2191
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_STORM-2D2191&d=DwMFaQ&c=LNdz7nrxyGFUIUTz2qIULQ&r=cPg4mUupZEtURFK34GyDCtRjHoUmKrI7oHRZqAh3hZY&m=WLOm6VPJkmQ40D2AN0W2qLgpsO_EMMUs1tPY-ZmYsxU&s=nIEeLQ791cIUCrbWmmplg7P1AgashM_PCr6M262i0q4&e=>
> for more details about it.
>
> Thanks,
>
> Bobby
>
>
> On Tue, Mar 27, 2018 at 8:45 AM Ramin Farajollah (BLOOMBERG/ 731 LEX) <
> rfarajollah@bloomberg.net> wrote:
>
>> Hi,
>>
>> when Storm runs, it sets up the command line with full path of all jars
>> to be included in the classpath.
>>
>> How can I simplify the command line by specifying directories and
>> wildcard where the jars reside?
>> In doing that, does Storm care about the order of the jars in cp?
>>
>>
>>
Re: Long command line
Posted by Bobby Evans <bo...@apache.org>.
Sorry this is a late reply.
There is no way to switch the classpath over to wildcards without changing
the code in storm.py.
In newer versions of storm that has been done. You can see
https://issues.apache.org/jira/browse/STORM-2191 for more details about it.
Thanks,
Bobby
On Tue, Mar 27, 2018 at 8:45 AM Ramin Farajollah (BLOOMBERG/ 731 LEX) <
rfarajollah@bloomberg.net> wrote:
> Hi,
>
> when Storm runs, it sets up the command line with full path of all jars to
> be included in the classpath.
>
> How can I simplify the command line by specifying directories and wildcard
> where the jars reside?
> In doing that, does Storm care about the order of the jars in cp?
>
>
>