[
https://issues.apache.org/jira/browse/SAMOA-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14666231#comment-14666231
]
ASF GitHub Bot commented on SAMOA-29:
-------------------------------------
Github user gdfm commented on the pull request:
https://github.com/apache/incubator-samoa/pull/34#issuecomment-129140660
@jayadeepj this second alternative seems reasonable.
In the end, the bin/samoa script already assumes that the properties file
are in the same dir (so it knows where they are and can add them to the
classpath).
> Remove hardcoded value for the duration of Storm local topology execution
> -------------------------------------------------------------------------
>
> Key: SAMOA-29
> URL: https://issues.apache.org/jira/browse/SAMOA-29
> Project: SAMOA
> Issue Type: Bug
> Components: SAMOA-Storm
> Reporter: Gianmarco De Francisci Morales
>
> From GitHub:
> In Storm local mode, the topology always executes for at most 10 minutes.
> Refer to com.yahoo.labs.samoa.LocalStormDoTask line 72.
> Possible solutions:
> 1) Add a new option to determine local topology execution duration in
> bin\samoa-storm.properties, use bin\samoa to parse the new option and pass to
> LocalStormDoTask as program argument.
> 2) Add the same new option as solution 1, use commons-configuration package
> to parse bin\samoa-storm.properties.
> For the second solution, we modify LocalStormDoTask to read the
> samoa-storm.properties using PropertiesConfiguration class of Apache
> commons-configuration. It will eliminate bash-code parsing in bin/samoa for
> all options except for $MODE_ARG.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
