Hi!
Thank for your reply. Yes there is a solution to put the config.properties
in the jar file and loaded with the Java API
getClasssLoader().getResourcesAsStream("config.properties"). I'm performing
many tests with fifferent configurations and rather than packaging all the
time the project, I prefer to send them as arguments for the topology. But
is seems that I have to live with this limitation of the command line. I
can send also the parameter for VM for taking my configuration file, thus I
can edit my configuration (via -Dconfig.path=config.properties). But I
believe that there is a simple solution.
Best regards,
Florin
On Wed, Sep 10, 2014 at 1:54 PM, 潘臻轩 <zhenxuan...@gmail.com> wrote:
> why don't you use config.properties ?
>
> 2014-09-10 18:40 GMT+08:00 Spico Florin <spicoflo...@gmail.com>:
>
>> Hello!
>> I have a topology that can take as input many arguments (more than 9)
>> set up in the storm.cmd line. How can I overpass this limitation without
>> the brute force on the storm.cmd command (by adding there more parameters
>> as I needed)?
>>
>> I look forward for your answers.
>> Regards,
>> Florin
>>
>
>
