Github user javrasya commented on the pull request:
https://github.com/apache/storm/pull/316#issuecomment-64173340
@harshach , change is actually because of setting that timeout value in
code simply. Environment variable can not be set in code. But property can be
set.
```
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/316#issuecomment-64175854
@javrasya I added trackedWait to have timeout-ms as parameter, but not
completeTopology.
Then we should add a parameter to completeTopology complete-topology to
[
https://issues.apache.org/jira/browse/STORM-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14222948#comment-14222948
]
ASF GitHub Bot commented on STORM-572:
--
GitHub user thinker0 opened a pull request:
Ahmet DAL created STORM-573:
---
Summary: Allow users to pass TEST-TIMEOUT-MS as param for
complete-topology
Key: STORM-573
URL: https://issues.apache.org/jira/browse/STORM-573
Project: Apache Storm
[
https://issues.apache.org/jira/browse/STORM-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ahmet DAL updated STORM-573:
Description: timeout value can be defined for complete-topology in
testing.clj. But not for the function
[
https://issues.apache.org/jira/browse/STORM-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ahmet DAL reassigned STORM-573:
---
Assignee: Ahmet DAL
Allow users to pass TEST-TIMEOUT-MS as param for complete-topology for Java
[
https://issues.apache.org/jira/browse/STORM-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ahmet DAL updated STORM-573:
Labels: test (was: )
Allow users to pass TEST-TIMEOUT-MS as param for complete-topology for Java
[
https://issues.apache.org/jira/browse/STORM-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ahmet DAL updated STORM-573:
Description: timeout value can be defined for complete-topology in
testing.clj after STORM-354 is fixed. But
[
https://issues.apache.org/jira/browse/STORM-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ahmet DAL updated STORM-573:
Priority: Minor (was: Major)
Allow users to pass TEST-TIMEOUT-MS as param for complete-topology for Java
Github user javrasya commented on the pull request:
https://github.com/apache/storm/pull/316#issuecomment-64191337
@HeartSaVioR you are right. This is better solution to add that parameter
to `complete-topology` in testing4j.clj. I added this capability to the
function but not
Github user javrasya closed the pull request at:
https://github.com/apache/storm/pull/316
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
[
https://issues.apache.org/jira/browse/STORM-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14222981#comment-14222981
]
ASF GitHub Bot commented on STORM-492:
--
Github user javrasya closed the pull request
GitHub user javrasya opened a pull request:
https://github.com/apache/storm/pull/327
[STORM-573]Allow users to pass TEST-TIMEOUT-MS as param for
complete-topology for Java
`timeout-ms` value can be passed as param to `comlete-topology` in
testing4j.clj for Java projects now.
You
[
https://issues.apache.org/jira/browse/STORM-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14222986#comment-14222986
]
ASF GitHub Bot commented on STORM-573:
--
GitHub user javrasya opened a pull request:
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/326#issuecomment-64202552
+1. Thanks @thinker0
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
[
https://issues.apache.org/jira/browse/STORM-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14223028#comment-14223028
]
ASF GitHub Bot commented on STORM-572:
--
Github user harshach commented on the pull
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/326#issuecomment-64204687
Looks good to me!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
[
https://issues.apache.org/jira/browse/STORM-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14223032#comment-14223032
]
ASF GitHub Bot commented on STORM-572:
--
Github user HeartSaVioR commented on the pull
[
https://issues.apache.org/jira/browse/STORM-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14223101#comment-14223101
]
Frantz Mazoyer commented on STORM-248:
--
Hello,
I would like to lift this limitation
[
https://issues.apache.org/jira/browse/STORM-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Frantz Mazoyer reassigned STORM-248:
Assignee: Frantz Mazoyer
cluster.xml location is hardcoded for workers.
[
https://issues.apache.org/jira/browse/STORM-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14223116#comment-14223116
]
Frantz Mazoyer commented on STORM-248:
--
Hello,
I would like to lift this limitation
[
https://issues.apache.org/jira/browse/STORM-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14223126#comment-14223126
]
Sriharsha Chintalapani commented on STORM-248:
--
[~fmazoyer] how about making
Github user Parth-Brahmbhatt commented on the pull request:
https://github.com/apache/storm/pull/326#issuecomment-64232856
+1
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
[
https://issues.apache.org/jira/browse/STORM-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb reopened STORM-524:
Copy-paste error:
nameApache Kafka/name
Please create a DOAP file for your TLP
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/327#issuecomment-64278289
Looks good to me.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user tedxia commented on the pull request:
https://github.com/apache/storm/pull/322#issuecomment-64302867
This PR is similar to
[STORM-253](https://issues.apache.org/jira/browse/STORM-253), but use different
solution, @clockfly can you have a look at this, thank you.
---
If
[
https://issues.apache.org/jira/browse/STORM-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14223972#comment-14223972
]
ASF GitHub Bot commented on STORM-564:
--
Github user tedxia commented on the pull
Github user rick-kilgore commented on the pull request:
https://github.com/apache/storm/pull/254#issuecomment-64317893
This PR is now update to incorporate most of the changes suggested by
@wurstmeister. I also discovered that the conflict I was worried about with
[
https://issues.apache.org/jira/browse/STORM-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14224126#comment-14224126
]
ASF GitHub Bot commented on STORM-495:
--
Github user rick-kilgore commented on the pull
29 matches
Mail list logo
