[
https://issues.apache.org/jira/browse/STORM-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257928#comment-14257928
]
ASF GitHub Bot commented on STORM-596:
--
GitHub user caofangkun opened a pull request:
GitHub user caofangkun opened a pull request:
https://github.com/apache/storm/pull/363
STORM-596: remove config topology.receiver.buffer.size
topology.receiver.buffer.size has no effect and not necessary for now.
Should we just remove it ?
You can merge this pull request into a
[
https://issues.apache.org/jira/browse/STORM-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TonyLee closed STORM-604.
-
Resolution: Won't Fix
error dashboard,sorry for that
> Storm Bug List
> --
>
> Key: ST
TonyLee created STORM-604:
-
Summary: Storm Bug List
Key: STORM-604
URL: https://issues.apache.org/jira/browse/STORM-604
Project: Apache Storm
Issue Type: Bug
Reporter: TonyLee
--
Th
[
https://issues.apache.org/jira/browse/STORM-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
caofangkun updated STORM-552:
-
Summary: add new config storm.messaging.netty.socket.backlog (was: add new
config storm.messaging.netty.ba
Github user caofangkun closed the pull request at:
https://github.com/apache/storm/pull/362
---
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 e
[
https://issues.apache.org/jira/browse/STORM-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257879#comment-14257879
]
ASF GitHub Bot commented on STORM-552:
--
Github user caofangkun commented on the pull r
Github user caofangkun commented on the pull request:
https://github.com/apache/storm/pull/311#issuecomment-68022108
@revans2
Thank you for your explanation and good advise .
I have renamed storm.messaging.netty.backlog,default to
storm.messaging.netty.socket.backlog and up
GitHub user caofangkun opened a pull request:
https://github.com/apache/storm/pull/362
Merge pull request #2 from apache/master
Merge from trunk to caofangkun
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/caofangkun/apache-storm
[
https://issues.apache.org/jira/browse/STORM-603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257682#comment-14257682
]
ASF GitHub Bot commented on STORM-603:
--
GitHub user curtisallen opened a pull request:
GitHub user curtisallen opened a pull request:
https://github.com/apache/storm/pull/361
STORM-603 Log errors when required kafka params are missing
https://issues.apache.org/jira/browse/STORM-603
I was upgrading our topologies to storm-0.9.3 this
[commit](https://github.com
Curtis Allen created STORM-603:
--
Summary: storm-kafka: Log errors when missing required
configuration fields
Key: STORM-603
URL: https://issues.apache.org/jira/browse/STORM-603
Project: Apache Storm
[
https://issues.apache.org/jira/browse/STORM-598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257578#comment-14257578
]
ASF GitHub Bot commented on STORM-598:
--
Github user revans2 commented on the pull requ
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/355#issuecomment-68001550
Also I tried to reproduce the issue on master and I am seeing the second
topology come up on the ui without any issues. Could you try to reproduce the
error on master and
[
https://issues.apache.org/jira/browse/STORM-598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257550#comment-14257550
]
ASF GitHub Bot commented on STORM-598:
--
Github user revans2 commented on a diff in the
Github user revans2 commented on a diff in the pull request:
https://github.com/apache/storm/pull/355#discussion_r22236169
--- Diff: storm-core/src/clj/backtype/storm/daemon/nimbus.clj ---
@@ -1248,7 +1256,7 @@
(when-let [owner (:o
[
https://issues.apache.org/jira/browse/STORM-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257536#comment-14257536
]
clay teahouse commented on STORM-602:
-
Further information on the issue:
1) When starti
[
https://issues.apache.org/jira/browse/STORM-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257528#comment-14257528
]
ASF GitHub Bot commented on STORM-599:
--
Github user revans2 commented on the pull requ
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/356#issuecomment-67997939
The changes look fine to me. My only concern would be around what happens
if the cache has not been updated and is empty, but it looks like it will
return an empty map, a
[
https://issues.apache.org/jira/browse/STORM-591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257521#comment-14257521
]
ASF GitHub Bot commented on STORM-591:
--
Github user revans2 commented on the pull requ
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/352#issuecomment-67997538
This seems to be used by the tests, after this change see a lot of DEBUG
and INFO logs from zookeeper. Instead of deleting it, can we move it to a
directory that is only
Github user Parth-Brahmbhatt commented on the pull request:
https://github.com/apache/storm/pull/318#issuecomment-67995761
actually there were multiple places with url-encode function that needed to
be replaced I have opened a PR so the issue no longer appears
https://github.com/apach
GitHub user Parth-Brahmbhatt opened a pull request:
https://github.com/apache/storm/pull/360
Storm-456: changing encoding to ring/url-encode.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Parth-Brahmbhatt/incubator-storm Storm-
[
https://issues.apache.org/jira/browse/STORM-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257411#comment-14257411
]
ASF GitHub Bot commented on STORM-442:
--
Github user revans2 commented on the pull requ
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/305#issuecomment-67989780
I see this has not had that much traffic in quite a while. The code to me
looks acceptable. I am not really happy with calling .available() twice, but I
can live with it
clay teahouse created STORM-602:
---
Summary: HdfsBolt dies when the hadoop node is not available
Key: STORM-602
URL: https://issues.apache.org/jira/browse/STORM-602
Project: Apache Storm
Issue Ty
[
https://issues.apache.org/jira/browse/STORM-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257341#comment-14257341
]
ASF GitHub Bot commented on STORM-243:
--
Github user revans2 commented on the pull requ
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/294#issuecomment-67985049
@caofangkun thank you for submitting this patch. I appreciate you trying
to help. In the future it would be good though, to be sure that your patch
complies and the unit
[
https://issues.apache.org/jira/browse/STORM-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257335#comment-14257335
]
ASF GitHub Bot commented on STORM-243:
--
Github user revans2 commented on a diff in the
Github user revans2 commented on a diff in the pull request:
https://github.com/apache/storm/pull/294#discussion_r8357
--- Diff: storm-dist/binary/src/main/assembly/binary.xml ---
@@ -131,13 +131,6 @@
-${project.basedir}/
[
https://issues.apache.org/jira/browse/STORM-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257328#comment-14257328
]
ASF GitHub Bot commented on STORM-243:
--
Github user revans2 commented on a diff in the
Github user revans2 commented on a diff in the pull request:
https://github.com/apache/storm/pull/294#discussion_r8250
--- Diff: storm-core/src/saveVersion.sh ---
@@ -0,0 +1,42 @@
+s file is used to generate the package-info.java class that
+# records the version, revisi
[
https://issues.apache.org/jira/browse/STORM-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257325#comment-14257325
]
ASF GitHub Bot commented on STORM-243:
--
Github user revans2 commented on a diff in the
Github user revans2 commented on a diff in the pull request:
https://github.com/apache/storm/pull/294#discussion_r8158
--- Diff: storm-core/src/clj/backtype/storm/ui/core.clj ---
@@ -52,15 +52,9 @@
(map #(.get_stats ^ExecutorSummary %))
(filter not-nil?))
[
https://issues.apache.org/jira/browse/STORM-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257304#comment-14257304
]
ASF GitHub Bot commented on STORM-248:
--
Github user revans2 commented on the pull requ
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/353#issuecomment-67982494
+1 the changes look fine to me. Please upmerge. the storm python script
has changed since you did the pull request and there are some minor merge
conflicts that should b
Probably the best thing to do for this is to file a JIRA at issues.apache.org
under STORM and include what it takes to reproduce the issue. - Bobby
On Tuesday, December 23, 2014 11:42 AM, clay teahouse
wrote:
Hi All,
Why HdfsBolt doesn't retry when the hadoop node is down or not a
[
https://issues.apache.org/jira/browse/STORM-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans resolved STORM-505.
---
Resolution: Fixed
Fix Version/s: 0.10.0
Thanks Derek,
I merged this into master
[
https://issues.apache.org/jira/browse/STORM-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257272#comment-14257272
]
ASF GitHub Bot commented on STORM-505:
--
Github user revans2 commented on the pull requ
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/359#issuecomment-67979768
+1 this is a rebase of https://github.com/apache/storm/pull/266
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as w
[
https://issues.apache.org/jira/browse/STORM-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257265#comment-14257265
]
ASF GitHub Bot commented on STORM-505:
--
GitHub user d2r opened a pull request:
ht
GitHub user d2r opened a pull request:
https://github.com/apache/storm/pull/359
STORM-505: Fix debug string construction
This pull request supersedes #266.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/d2r/storm STORM-505
Alter
[
https://issues.apache.org/jira/browse/STORM-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257260#comment-14257260
]
ASF GitHub Bot commented on STORM-505:
--
Github user d2r closed the pull request at:
Hi All,
Why HdfsBolt doesn't retry when the hadoop node is down or not accessible
and dies brings down the topology with it too? I can catch the run time
exception and keep the topology going, but was wondering why the retry is
not built into HdfsBolt.
thank you
Clay
Github user d2r closed the pull request at:
https://github.com/apache/storm/pull/266
---
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 enabled
[
https://issues.apache.org/jira/browse/STORM-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257261#comment-14257261
]
ASF GitHub Bot commented on STORM-505:
--
Github user d2r commented on the pull request:
Github user d2r commented on the pull request:
https://github.com/apache/storm/pull/266#issuecomment-67978120
Will open a New PR against master.
---
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 hav
[
https://issues.apache.org/jira/browse/STORM-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257254#comment-14257254
]
ASF GitHub Bot commented on STORM-552:
--
Github user revans2 commented on the pull requ
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/311#issuecomment-67976914
@caofangkun any update on this?
---
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 ha
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/318#issuecomment-67976452
The issue appears to be that when we url decode the topology name the '+'
is staying as a '+' if I replace it with a space ' ' in the URL it seems to
work for me on both f
[
https://issues.apache.org/jira/browse/STORM-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans resolved STORM-577.
---
Resolution: Fixed
Fix Version/s: 0.10.0
Thanks [~xiajun] I merged this into mast
[
https://issues.apache.org/jira/browse/STORM-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257219#comment-14257219
]
ASF GitHub Bot commented on STORM-577:
--
Github user asfgit closed the pull request at:
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/332
---
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-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257180#comment-14257180
]
ASF GitHub Bot commented on STORM-595:
--
Github user Parth-Brahmbhatt commented on the
Github user Parth-Brahmbhatt commented on the pull request:
https://github.com/apache/storm/pull/351#issuecomment-67970628
+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
enab
[
https://issues.apache.org/jira/browse/STORM-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257159#comment-14257159
]
ASF GitHub Bot commented on STORM-595:
--
Github user harshach commented on the pull req
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/351#issuecomment-67968645
+1. 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 f
[
https://issues.apache.org/jira/browse/STORM-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257151#comment-14257151
]
ASF GitHub Bot commented on STORM-575:
--
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/STORM-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans resolved STORM-575.
---
Resolution: Fixed
Fix Version/s: 0.10.0
[~msiegel07] Sorry it took me so long to
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/334
---
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-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans updated STORM-575:
--
Assignee: Matthew Siegel
> Ability to specify Jetty host to bind to
> ---
[
https://issues.apache.org/jira/browse/STORM-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Thomsen resolved STORM-595.
Resolution: Implemented
> storm-hdfs can only work with sequence files that use Writables
> -
[
https://issues.apache.org/jira/browse/STORM-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257133#comment-14257133
]
Robert Joseph Evans commented on STORM-544:
---
I checked the changes into http://sv
[
https://issues.apache.org/jira/browse/STORM-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans resolved STORM-544.
---
Resolution: Fixed
Fix Version/s: 0.10.0
> Some documents from website are outdat
[
https://issues.apache.org/jira/browse/STORM-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257100#comment-14257100
]
Robert Joseph Evans commented on STORM-544:
---
I just merged this into the master b
[
https://issues.apache.org/jira/browse/STORM-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257097#comment-14257097
]
ASF GitHub Bot commented on STORM-544:
--
Github user revans2 commented on the pull requ
[
https://issues.apache.org/jira/browse/STORM-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257099#comment-14257099
]
ASF GitHub Bot commented on STORM-544:
--
Github user asfgit closed the pull request at:
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/340
---
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
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/340#issuecomment-67962843
+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 w
[
https://issues.apache.org/jira/browse/STORM-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257087#comment-14257087
]
ASF GitHub Bot commented on STORM-601:
--
GitHub user revans2 opened a pull request:
GitHub user revans2 opened a pull request:
https://github.com/apache/storm/pull/358
STORM-601: Make jira-github-join ignore case.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/revans2/incubator-storm STORM-601
Alternatively yo
Robert Joseph Evans created STORM-601:
-
Summary: Have jira-github-join ignore case in matting JIRA number
Key: STORM-601
URL: https://issues.apache.org/jira/browse/STORM-601
Project: Apache Storm
You could add yourself to the powered by page
http://storm.apache.org/documentation/Powered-By.html
We recently moved the documentation source into git so you can fork storm and
update
https://github.com/apache/storm/blob/master/docs/documentation/Powered-By.md
Then put up a pull request for the
Hi,
Quite interested in this project. do we need to explore OpenCV to run the
examples ?
On Tue, Dec 23, 2014 at 3:35 PM, Corné Versloot
wrote:
> Hi Storm dev's,
>
> A couple of colleagues and myself have developed a computer vision specific
> 'extension' of Storm called StormCV which can be us
Hi Storm dev's,
A couple of colleagues and myself have developed a computer vision specific
'extension' of Storm called StormCV which can be used to create large scale
video analysis topologies. It includes its own model, serializers and
supports the use of the OpenCV library for image enhancement
75 matches
Mail list logo
