[
https://issues.apache.org/jira/browse/STORM-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Zhong resolved STORM-422.
--
Resolution: Fixed
Fix Version/s: 0.9.3-rc2
Committed. Thanks, Megan.
> storm.cmd limits the numbe
[
https://issues.apache.org/jira/browse/STORM-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195839#comment-14195839
]
Sean Zhong commented on STORM-422:
--
committed at b64e7b7a74126f5dbf01ff257090f6396ed38ab2
[
https://issues.apache.org/jira/browse/STORM-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195831#comment-14195831
]
ASF GitHub Bot commented on STORM-422:
--
Github user asfgit closed the pull request at:
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/201
---
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 enabl
[
https://issues.apache.org/jira/browse/STORM-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195822#comment-14195822
]
ASF GitHub Bot commented on STORM-535:
--
Github user clockfly commented on the pull req
Github user clockfly commented on the pull request:
https://github.com/apache/storm/pull/298#issuecomment-61601572
@caofangkun
User can set native lib by config option:
```
confvalue("java.library.path", extrajars),
```
Should that be flexible enough?
Github user clockfly commented on the pull request:
https://github.com/apache/storm/pull/292#issuecomment-61601001
@lukedemi
Please add the JIRA number to the title of the pull request?
---
If your project is set up for it, you can reply to this email and have your
reply app
[
https://issues.apache.org/jira/browse/STORM-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195812#comment-14195812
]
ASF GitHub Bot commented on STORM-253:
--
GitHub user clockfly reopened a pull request:
GitHub user clockfly reopened a pull request:
https://github.com/apache/storm/pull/45
STORM-253: Allow storm worker to use dynamic port instead of pre-configed.
Add a ne...
PR for [STORM-253](https://issues.apache.org/jira/browse/STORM-253)
Allow supervisor to decide worker
Github user clockfly commented on the pull request:
https://github.com/apache/storm/pull/292#issuecomment-61600425
+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
enabled and
[
https://issues.apache.org/jira/browse/STORM-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195808#comment-14195808
]
ASF GitHub Bot commented on STORM-329:
--
Github user clockfly commented on the pull req
Github user clockfly commented on the pull request:
https://github.com/apache/storm/pull/268#issuecomment-61600325
@nathanmarz @revans2
Do you want to take a look at it?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
[
https://issues.apache.org/jira/browse/STORM-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195806#comment-14195806
]
ASF GitHub Bot commented on STORM-493:
--
Github user clockfly commented on the pull req
Github user clockfly commented on the pull request:
https://github.com/apache/storm/pull/252#issuecomment-61600229
@revans2, looks like you mark it as resolved. Have you merged ths into
trunk in other PR?
---
If your project is set up for it, you can reply to this email and have your
[
https://issues.apache.org/jira/browse/STORM-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195793#comment-14195793
]
ASF GitHub Bot commented on STORM-188:
--
Github user clockfly commented on the pull req
Github user clockfly commented on the pull request:
https://github.com/apache/storm/pull/120#issuecomment-61599764
@d2r , sorry it takes so long.
Now, the patch is synced with upstream.
---
If your project is set up for it, you can reply to this email and have your
repl
[
https://issues.apache.org/jira/browse/STORM-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Zhong resolved STORM-497.
--
Resolution: Fixed
Fix Version/s: 0.9.3-rc2
> b.s.m.netty.Server.getMessageQueueId is not thread sa
[
https://issues.apache.org/jira/browse/STORM-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195683#comment-14195683
]
ASF GitHub Bot commented on STORM-497:
--
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/STORM-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195684#comment-14195684
]
Sean Zhong commented on STORM-497:
--
commited at cb53d478448544ee18d258bb4ce1951c99a8ed87.
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/257
---
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 enabl
[
https://issues.apache.org/jira/browse/STORM-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195583#comment-14195583
]
ASF GitHub Bot commented on STORM-497:
--
Github user HeartSaVioR commented on the pull
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/257#issuecomment-61584109
@clockfly @revans2
I've found that I've misunderstand this patch. Comment 2 is wrong, sorry
about it.
Regarding comment 1, if performance is not a concern, it'
[
https://issues.apache.org/jira/browse/STORM-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195527#comment-14195527
]
ASF GitHub Bot commented on STORM-497:
--
Github user clockfly commented on the pull req
Github user clockfly commented on the pull request:
https://github.com/apache/storm/pull/257#issuecomment-61579721
@HeartSaVioR,
The performance is not a concern, since taskToQueueId will only be modified
for a few times.
+1 for the patch
---
If your project is set
I skimmed some files of storm-redis, but I'm still curious that what's the
key point from storm-redis.
So I have some questions.
- Is Redis for skipping completed tuples when root tuple is replayed, or
continue processing tuple from last state?
- Do users need to handle states it by his/her hand?
I am curious what this project offers over using a redis client directly? Or
compared to writing a trident state implementation for redis? - Bobby
On Monday, November 3, 2014 2:35 PM, Abhishek Bhattacharjee
wrote:
Hi,
We ( me and the CCed persons) are maintaining a project on githu
Hi,
We ( me and the CCed persons) are maintaining a project on github
which manages to implement stateful-ness in storm.
We have got some encouraging results through our benchmarking.
We would like to know what more could be done so that the project could
be inculcated into @stormprocessor
Github
Here is what has worked for me:
cd storm-core
mvn clojure:repl
(use 'clojure.test)
(use '<>)
(run-tests '<>)
Ref:
https://github.com/apache/storm/pull/14#issuecomment-31481945
--
Derek
On Friday, October 31, 2014 7:04 AM, koray mehmet
wrote:
how do I able to run repl and test through r
[
https://issues.apache.org/jira/browse/STORM-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14194636#comment-14194636
]
Sean Zhong commented on STORM-350:
--
I use 3 task on same worker process. (1 spout -> 1 bo
[
https://issues.apache.org/jira/browse/STORM-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14194517#comment-14194517
]
koray sariteke edited comment on STORM-248 at 11/3/14 1:20 PM:
--
[
https://issues.apache.org/jira/browse/STORM-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14194517#comment-14194517
]
koray sariteke commented on STORM-248:
--
I got it as a first step in storm.
> cluster.
Michał Kozak created STORM-545:
--
Summary: DRCP does not return a cause of failure
Key: STORM-545
URL: https://issues.apache.org/jira/browse/STORM-545
Project: Apache Storm
Issue Type: Wish
A
I think I can give you an idea.
You can emit several times in a unique tuple processing.
Do a "for loop", and execute "emit" function inside the loop to emit
multiple tuples.
On 3 November 2014 12:42, clay teahouse wrote:
> Hello All,
> Is it possible emit batches of tuples, as opposed to one
Hello All,
Is it possible emit batches of tuples, as opposed to one tuple at a time?
In other word, is it possible to batch the tuples before emitting them? An
application for batching the tuples is for example for writing the tuples
to a tcp socket but not wanting to do a flush after each tuple i
[
https://issues.apache.org/jira/browse/STORM-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14194377#comment-14194377
]
ASF GitHub Bot commented on STORM-442:
--
Github user HeartSaVioR commented on the pull
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/305#issuecomment-61453891
@dashengju
Yes, ShellSpout/Bolt read stderr from subprocess after sending tuple
immediately.
I'm afraid that this may cannot cover all cases, and ShellBol
36 matches
Mail list logo
