Github user jerrypeng commented on a diff in the pull request:
https://github.com/apache/storm/pull/675#discussion_r36867859
--- Diff: storm-core/src/ui/public/templates/topology-page-template.html ---
@@ -313,6 +320,10 @@
/th
th class=headerLast error
Github user jerrypeng commented on the pull request:
https://github.com/apache/storm/pull/675#issuecomment-130327785
---
If your project is
[
https://issues.apache.org/jira/browse/STORM-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14693612#comment-14693612
]
ASF GitHub Bot commented on STORM-949:
--
Github user jerrypeng commented on the pull
[
https://issues.apache.org/jira/browse/STORM-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14693609#comment-14693609
]
ASF GitHub Bot commented on STORM-949:
--
Github user jerrypeng commented on a diff in
Github user jerrypeng commented on the pull request:
https://github.com/apache/storm/pull/675#issuecomment-130347080
fixed the formating issues
---
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
[
https://issues.apache.org/jira/browse/STORM-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14693695#comment-14693695
]
ASF GitHub Bot commented on STORM-949:
--
Github user jerrypeng commented on the pull
Github user ptgoetz commented on the pull request:
https://github.com/apache/storm/pull/670#issuecomment-130444965
I have a few things that I think need to be fixed before we publish this.
But rather than enumerate every last little thing and ask you to fix them, I'd
rather jump in
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/670#issuecomment-130447771
@ptgoetz if these issues are layout please list them out we can send a new
patch. I don't think website layout needs to be blocked on docs or other fixes.
I want to see
Github user zhuoliu commented on the pull request:
https://github.com/apache/storm/pull/572#issuecomment-130454722
Thanks @lazyval for the comments, we may file a separate jira to do some
follow-up work for this as needed.
---
If your project is set up for it, you can reply to this
[
https://issues.apache.org/jira/browse/STORM-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14694064#comment-14694064
]
Jon Weygandt commented on STORM-594:
Do you have a link to this paper?
Auto-Scaling
Github user Parth-Brahmbhatt commented on the pull request:
https://github.com/apache/storm/pull/354#issuecomment-130450409
@revans2 @ptgoetz @harshach I have merged with master one more time. We are
still using curator's LeaderLatch recipe. Nimbus discovery is done via an API
so all
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/670#issuecomment-130488992
@ptgoetz will look into the fb goog calls and also generating the news
feed. As far as separate branch goes thats fine by me but another issue could
be that the doc
[
https://issues.apache.org/jira/browse/STORM-980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14693924#comment-14693924
]
ASF GitHub Bot commented on STORM-980:
--
Github user asfgit closed the pull request at:
Github user ptgoetz commented on the pull request:
https://github.com/apache/storm/pull/670#issuecomment-130452561
@harshach I'm not suggesting we create a feature branch, I'm suggesting we
change the way we publish the site to make it easier for people to contribute
to. I forgot to
[
https://issues.apache.org/jira/browse/STORM-977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14694269#comment-14694269
]
Gabor Liptak commented on STORM-977:
https://en.wikipedia.org/wiki/Unix_signal
Github user caofangkun commented on a diff in the pull request:
https://github.com/apache/storm/pull/680#discussion_r36937217
--- Diff: storm-core/src/clj/backtype/storm/timer.clj ---
@@ -53,8 +53,11 @@
;; event generation. If any recurring
[
https://issues.apache.org/jira/browse/STORM-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14694633#comment-14694633
]
ASF GitHub Bot commented on STORM-974:
--
Github user caofangkun commented on a diff in
[
https://issues.apache.org/jira/browse/STORM-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14694625#comment-14694625
]
ASF GitHub Bot commented on STORM-974:
--
Github user caofangkun commented on a diff in
Github user caofangkun commented on a diff in the pull request:
https://github.com/apache/storm/pull/679#discussion_r36938144
--- Diff:
external/storm-elasticsearch/src/main/java/org/apache/storm/elasticsearch/trident/EsStateFactory.java
---
@@ -19,6 +19,7 @@
import
Github user caofangkun commented on a diff in the pull request:
https://github.com/apache/storm/pull/679#discussion_r36938292
--- Diff:
external/storm-elasticsearch/src/test/java/org/apache/storm/elasticsearch/bolt/EsPercolateBoltTest.java
---
@@ -21,6 +21,7 @@
import
[
https://issues.apache.org/jira/browse/STORM-977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Liptak reassigned STORM-977:
--
Assignee: Gabor Liptak
Incorrect signal (-9) when as-user is true
caofangkun created STORM-988:
Summary: supervisor.slots.ports should not allow duplicate element
values
Key: STORM-988
URL: https://issues.apache.org/jira/browse/STORM-988
Project: Apache Storm
Github user caofangkun commented on a diff in the pull request:
https://github.com/apache/storm/pull/679#discussion_r36938034
--- Diff:
external/storm-elasticsearch/src/main/java/org/apache/storm/elasticsearch/bolt/EsPercolateBolt.java
---
@@ -31,14 +32,21 @@
--- End
Github user wangli1426 commented on a diff in the pull request:
https://github.com/apache/storm/pull/680#discussion_r36938783
--- Diff: storm-core/src/clj/backtype/storm/timer.clj ---
@@ -53,8 +53,11 @@
;; event generation. If any recurring
[
https://issues.apache.org/jira/browse/STORM-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14694638#comment-14694638
]
ASF GitHub Bot commented on STORM-974:
--
Github user caofangkun commented on a diff in
Github user caofangkun commented on a diff in the pull request:
https://github.com/apache/storm/pull/679#discussion_r36938233
--- Diff:
external/storm-elasticsearch/src/test/java/org/apache/storm/elasticsearch/bolt/EsIndexBoltTest.java
---
@@ -20,6 +20,7 @@
import
[
https://issues.apache.org/jira/browse/STORM-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14694629#comment-14694629
]
ASF GitHub Bot commented on STORM-974:
--
Github user caofangkun commented on a diff in
[
https://issues.apache.org/jira/browse/STORM-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14694189#comment-14694189
]
ASF GitHub Bot commented on STORM-950:
--
Github user ptgoetz commented on the pull
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/678#issuecomment-130508217
@randerzander Yes, right. I'll take care of it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
[
https://issues.apache.org/jira/browse/STORM-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14694154#comment-14694154
]
ASF GitHub Bot commented on STORM-950:
--
Github user ptgoetz commented on the pull
GitHub user caofangkun opened a pull request:
https://github.com/apache/storm/pull/681
STORM-988: supervisor.slots.ports should not allow duplicate element values
You can merge this pull request into a Git repository by running:
$ git pull
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/678#issuecomment-130212024
Seems like something is messed.
- https://github.com/apache/storm/pull/556
-
GitHub user randerzander opened a pull request:
https://github.com/apache/storm/pull/678
Corrected ConnectionPrvoider to ConnectionProvider
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/randerzander/storm master
Alternatively
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/678#issuecomment-130222094
My bad. Sorry, it seems to be just missed spot. ;)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/678#issuecomment-130223541
+1.
Since it modifies method name, it should be applied to 0.10.0 to keep
backward compatibility with 0.10.0 and 0.11.0.
---
If your project is set up for it,
Github user randerzander commented on the pull request:
https://github.com/apache/storm/pull/678#issuecomment-130236052
How do you want to handle the .10 update? Separate PR?
---
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-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14693732#comment-14693732
]
Boyang Jerry Peng commented on STORM-594:
-
Hello guys,
Recently there has been
[
https://issues.apache.org/jira/browse/STORM-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14693503#comment-14693503
]
ASF GitHub Bot commented on STORM-974:
--
GitHub user HeartSaVioR opened a pull request:
[
https://issues.apache.org/jira/browse/STORM-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14693521#comment-14693521
]
ASF GitHub Bot commented on STORM-837:
--
Github user revans2 commented on the pull
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/644#issuecomment-130315702
For me internally the tests pass and everything builds. Although the rest
of storm seems a bit unstable with tests.
I think the changes look fine +1 for merging
[
https://issues.apache.org/jira/browse/STORM-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14693536#comment-14693536
]
ASF GitHub Bot commented on STORM-851:
--
Github user harshach commented on a diff in
Github user harshach commented on a diff in the pull request:
https://github.com/apache/storm/pull/665#discussion_r36863654
--- Diff:
external/storm-solr/src/main/java/org/apache/storm/solr/bolt/AbstractSolrBolt.java
---
@@ -0,0 +1,33 @@
+package org.apache.storm.solr.bolt;
GitHub user wangli1426 opened a pull request:
https://github.com/apache/storm/pull/680
Update timer.clj
Issue description: The timer thread calculates the delay to schedule the
head of the queue and sleeps accordingly. However, if a new event with high
priority is inserted at the
GitHub user HeartSaVioR opened a pull request:
https://github.com/apache/storm/pull/679
STORM-974 Introduces Tuple - ES document mapper to get rid of constant
field mapping
* EsTupleMapper defines how to extract source, index, type, and id from
tuple for ElasticSearch.
*
Yes JDBC state has the same problem that I found in HDFS state recently. It is
ignoring the commits.
https://github.com/apache/storm/blob/master/external/storm-jdbc/src/main/java/org/apache/storm/jdbc/trident/state/JdbcState.java#L114-L122
Please file a JIRA to update JdbcState to make it
Github user d2r commented on the pull request:
https://github.com/apache/storm/pull/674#issuecomment-130387500
+1 on your testing of this. We can revert if it does not work.
---
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-980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14693922#comment-14693922
]
ASF GitHub Bot commented on STORM-980:
--
Github user d2r commented on the pull request:
[
https://issues.apache.org/jira/browse/STORM-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14693934#comment-14693934
]
Derek Dagit commented on STORM-798:
---
Linking the JIRA that probably fixed this issue.
Github user randerzander commented on the pull request:
https://github.com/apache/storm/pull/678#issuecomment-130415963
that's something you need to be comitter to do, right?
I'm not sure how to use one PR to commit to multiple branches.
---
If your project is set up for it,
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/666#issuecomment-130404466
+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
Sriharsha Chintalapani created STORM-987:
Summary: Document how to recover TopicOffsetOutOfRange exception
in Storm-Kafka Connector
Key: STORM-987
URL: https://issues.apache.org/jira/browse/STORM-987
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/674
---
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-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14693875#comment-14693875
]
Boyang Jerry Peng commented on STORM-893:
-
Through collaboration with people at
[
https://issues.apache.org/jira/browse/STORM-983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boyang Jerry Peng reassigned STORM-983:
---
Assignee: Boyang Jerry Peng
If stormconf.ser is not downloaded correctly, the
54 matches
Mail list logo
