[
https://issues.apache.org/jira/browse/STORM-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632299#comment-14632299
]
Linyuxin commented on STORM-950:
Looks beautiful and hierarchical.
But the font may be too
[
https://issues.apache.org/jira/browse/STORM-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632285#comment-14632285
]
ASF GitHub Bot commented on STORM-643:
--
Github user 2new commented on the pull request
Github user 2new commented on the pull request:
https://github.com/apache/storm/pull/642#issuecomment-122485021
+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 wis
[
https://issues.apache.org/jira/browse/STORM-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632274#comment-14632274
]
ASF GitHub Bot commented on STORM-918:
--
Github user bourneagain commented on the pull
Github user bourneagain commented on the pull request:
https://github.com/apache/storm/pull/632#issuecomment-122483857
Thanks for the comments, I understand the implication now and have changed
the code accordingly.
---
If your project is set up for it, you can reply to this email a
[
https://issues.apache.org/jira/browse/STORM-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632256#comment-14632256
]
ASF GitHub Bot commented on STORM-139:
--
Github user harshach commented on the pull req
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/641#issuecomment-122480198
+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-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632254#comment-14632254
]
ASF GitHub Bot commented on STORM-643:
--
Github user harshach commented on the pull req
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/642#issuecomment-122480095
+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-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632253#comment-14632253
]
ASF GitHub Bot commented on STORM-643:
--
Github user vesense commented on the pull requ
Github user vesense commented on the pull request:
https://github.com/apache/storm/pull/635#issuecomment-122479965
@HeartSaVioR
I have created a new PR(https://github.com/apache/storm/pull/642) based on
master branch. Could you take a look? Thx.
---
If your project is set up for
[
https://issues.apache.org/jira/browse/STORM-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632249#comment-14632249
]
ASF GitHub Bot commented on STORM-643:
--
GitHub user vesense opened a pull request:
GitHub user vesense opened a pull request:
https://github.com/apache/storm/pull/642
[STORM-643] KafkaUtils repeatedly fetches messages whose offset is out of
range
STORM-643 fixing based on master branch
You can merge this pull request into a Git repository by running:
$ git p
Github user vesense commented on the pull request:
https://github.com/apache/storm/pull/635#issuecomment-122479359
@HeartSaVioR Yeah, you are right. We can reproduce the issue with 0.10.x
branch too. And I will make a new PR based on master branch.
---
If your project is set up for i
[
https://issues.apache.org/jira/browse/STORM-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632242#comment-14632242
]
ASF GitHub Bot commented on STORM-643:
--
Github user vesense commented on the pull requ
[
https://issues.apache.org/jira/browse/STORM-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim resolved STORM-67.
---
Resolution: Fixed
Fix Version/s: 0.11.0
Thanks [~shyamrajendran] for great work.
I merged this to
[
https://issues.apache.org/jira/browse/STORM-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632233#comment-14632233
]
ASF GitHub Bot commented on STORM-67:
-
Github user asfgit closed the pull request at:
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/593
---
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 HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/635#issuecomment-122468927
@vesense Though I don't know about storm-kafka deeply, seems like
ExponentialBackoffMsgRetryManager doesn't care about it. It just delays
retrying failed tuples, and
[
https://issues.apache.org/jira/browse/STORM-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632217#comment-14632217
]
ASF GitHub Bot commented on STORM-643:
--
Github user HeartSaVioR commented on the pull
[
https://issues.apache.org/jira/browse/STORM-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632215#comment-14632215
]
ASF GitHub Bot commented on STORM-643:
--
Github user vesense commented on the pull requ
Github user vesense commented on the pull request:
https://github.com/apache/storm/pull/635#issuecomment-122467741
Thanks for reminding. Yes, I'm working on 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 your proj
[
https://issues.apache.org/jira/browse/STORM-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632211#comment-14632211
]
ASF GitHub Bot commented on STORM-643:
--
Github user vesense closed the pull request at
Github user vesense closed the pull request at:
https://github.com/apache/storm/pull/405
---
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 enab
[
https://issues.apache.org/jira/browse/STORM-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632210#comment-14632210
]
ASF GitHub Bot commented on STORM-643:
--
Github user vesense commented on the pull requ
Github user vesense commented on the pull request:
https://github.com/apache/storm/pull/405#issuecomment-122466082
Will do. Thanks.
---
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 featur
[
https://issues.apache.org/jira/browse/STORM-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim resolved STORM-643.
Resolution: Fixed
Fix Version/s: 0.9.6
Thanks [~vesense], I merged into 0.9.x-branch.
Please
[
https://issues.apache.org/jira/browse/STORM-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632191#comment-14632191
]
ASF GitHub Bot commented on STORM-643:
--
Github user HeartSaVioR commented on the pull
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/405#issuecomment-122464841
@vesense I merged #635 to 0.9.x-branch. Could you close the PR? Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear o
[
https://issues.apache.org/jira/browse/STORM-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim updated STORM-643:
---
Summary: KafkaUtils repeatedly fetches messages whose offset is out of
range (for 0.9.x) (was: KafkaUt
[
https://issues.apache.org/jira/browse/STORM-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632190#comment-14632190
]
ASF GitHub Bot commented on STORM-643:
--
Github user asfgit closed the pull request at:
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/635
---
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-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632176#comment-14632176
]
ASF GitHub Bot commented on STORM-643:
--
Github user HeartSaVioR commented on the pull
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/635#issuecomment-122462058
+1. I'll merge it.
Please note that we're considering only 0.9.x now, so we should try to
reproduce and fix from 0.10.x and master later.
---
If your projec
[
https://issues.apache.org/jira/browse/STORM-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632149#comment-14632149
]
Sriharsha Chintalapani commented on STORM-950:
--
[~kabhwan] Thanks for the feed
[
https://issues.apache.org/jira/browse/STORM-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632129#comment-14632129
]
Jungtaek Lim commented on STORM-950:
Looks beautiful on my laptop!
Personally I really
[
https://issues.apache.org/jira/browse/STORM-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632121#comment-14632121
]
ASF GitHub Bot commented on STORM-139:
--
GitHub user d2r reopened a pull request:
GitHub user d2r reopened a pull request:
https://github.com/apache/storm/pull/641
[STORM-139] Correctly hash byte array tuple values
* Unit test for correctness is included
* The following tests showed no discernible difference in latency or
throughput:
* word_count, last
[
https://issues.apache.org/jira/browse/STORM-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632115#comment-14632115
]
ASF GitHub Bot commented on STORM-139:
--
Github user d2r closed the pull request at:
Github user d2r closed the pull request at:
https://github.com/apache/storm/pull/641
---
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-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632090#comment-14632090
]
ASF GitHub Bot commented on STORM-139:
--
GitHub user d2r opened a pull request:
ht
GitHub user d2r opened a pull request:
https://github.com/apache/storm/pull/641
[STORM-139] Correctly hash byte array tuple values
* Unit test for correctness is included
* The following tests showed no discernible difference in latency or
throughput:
* word_count, last 10
Sriharsha Chintalapani created STORM-951:
Summary: Storm Hive connector not aborting transactions incase of
failures
Key: STORM-951
URL: https://issues.apache.org/jira/browse/STORM-951
Project
[
https://issues.apache.org/jira/browse/STORM-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632000#comment-14632000
]
Sriharsha Chintalapani commented on STORM-950:
--
Thanks [~dagit]. I'll try to r
[
https://issues.apache.org/jira/browse/STORM-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631999#comment-14631999
]
Sriharsha Chintalapani commented on STORM-950:
--
Thanks [~dagit]. I'll try to r
[
https://issues.apache.org/jira/browse/STORM-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani updated STORM-950:
-
Comment: was deleted
(was: Thanks [~dagit]. I'll try to reproduce this. If its poss
[
https://issues.apache.org/jira/browse/STORM-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631987#comment-14631987
]
P. Taylor Goetz commented on STORM-950:
---
Keep in mind this is just a preview at the m
[
https://issues.apache.org/jira/browse/STORM-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631972#comment-14631972
]
Derek Dagit commented on STORM-950:
---
When the header bar attaches to the top of the windo
[
https://issues.apache.org/jira/browse/STORM-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631964#comment-14631964
]
Derek Dagit commented on STORM-950:
---
OK, just saw it happen for another user with a simil
[
https://issues.apache.org/jira/browse/STORM-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631961#comment-14631961
]
Derek Dagit commented on STORM-950:
---
Yeah, its FF 39.0 on OSX.
The size of the canvas is
[
https://issues.apache.org/jira/browse/STORM-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631935#comment-14631935
]
Sriharsha Chintalapani commented on STORM-950:
--
[~dagit] I tried it on Firefox
[
https://issues.apache.org/jira/browse/STORM-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631929#comment-14631929
]
Derek Dagit commented on STORM-950:
---
This is beautiful, nice work!
If I scroll to the bo
Sriharsha Chintalapani created STORM-950:
Summary: Apache Storm website redesign
Key: STORM-950
URL: https://issues.apache.org/jira/browse/STORM-950
Project: Apache Storm
Issue Type:
[
https://issues.apache.org/jira/browse/STORM-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631915#comment-14631915
]
Sriharsha Chintalapani commented on STORM-950:
--
Here is staging website with u
Reza Farivar created STORM-949:
--
Summary: On the topology summary UI page, last shown error should
have the time and date
Key: STORM-949
URL: https://issues.apache.org/jira/browse/STORM-949
Project: Apac
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/570#issuecomment-122277257
@chuanlei Thanks, it's my pleasure. :)
---
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
[
https://issues.apache.org/jira/browse/STORM-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631277#comment-14631277
]
Derek Dagit commented on STORM-728:
---
> I changed affect version and fix version from JIR
Eugene Tolmachev created STORM-948:
--
Summary: "topology.max.spout.pending" submitted with the component
configuration is ignored
Key: STORM-948
URL: https://issues.apache.org/jira/browse/STORM-948
Pr
Github user chuanlei commented on the pull request:
https://github.com/apache/storm/pull/570#issuecomment-122240118
@revans2 @HeartSaVioR
Thank you very much. @HeartSaVioR has helped me a lot in the Storm topic.
You can really patient and friendly to newbie to Storm.
---
If your
[
https://issues.apache.org/jira/browse/STORM-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631157#comment-14631157
]
ASF GitHub Bot commented on STORM-947:
--
Github user chuanlei commented on the pull req
Github user chuanlei commented on the pull request:
https://github.com/apache/storm/pull/640#issuecomment-122239340
I think it is good since `ExecutorDetails` does not take more information.
And this change make Storm code more concise.
But I'm sure whether `ExecutorDetails` i
[
https://issues.apache.org/jira/browse/STORM-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631154#comment-14631154
]
ASF GitHub Bot commented on STORM-947:
--
Github user chuanlei commented on a diff in th
Github user chuanlei commented on a diff in the pull request:
https://github.com/apache/storm/pull/640#discussion_r34878435
--- Diff: storm-core/src/clj/backtype/storm/scheduler/DefaultScheduler.clj
---
@@ -18,7 +18,7 @@
(:require [backtype.storm.scheduler.EvenScheduler :as
[
https://issues.apache.org/jira/browse/STORM-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631110#comment-14631110
]
ASF GitHub Bot commented on STORM-947:
--
GitHub user caofangkun opened a pull request:
GitHub user caofangkun opened a pull request:
https://github.com/apache/storm/pull/640
STORM-947: replace all `backtype.storm.scheduler.ExecutorDetails` with
`backtype.storm.generated.ExecutorInfo `
You can merge this pull request into a Git repository by running:
$ git pu
caofangkun created STORM-947:
Summary: replace all `backtype.storm.scheduler.ExecutorDetails`
with `backtype.storm.generated.ExecutorInfo `
Key: STORM-947
URL: https://issues.apache.org/jira/browse/STORM-947
[
https://issues.apache.org/jira/browse/STORM-946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14630919#comment-14630919
]
ASF GitHub Bot commented on STORM-946:
--
Github user tedxia commented on the pull reque
Github user tedxia commented on the pull request:
https://github.com/apache/storm/pull/639#issuecomment-122206400
Will you have a look at the description of this pull request, it describe
the situation.
---
If your project is set up for it, you can reply to this email and have your
[
https://issues.apache.org/jira/browse/STORM-946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14630903#comment-14630903
]
ASF GitHub Bot commented on STORM-946:
--
Github user caofangkun commented on the pull r
Github user caofangkun commented on the pull request:
https://github.com/apache/storm/pull/639#issuecomment-122203636
@tedxia
I could only find two situations ( am I right?) will change
```client.status``` to ```closed``` by call ```(.close socket)```. and do not
need reconnect
[
https://issues.apache.org/jira/browse/STORM-946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14630883#comment-14630883
]
ASF GitHub Bot commented on STORM-946:
--
Github user tedxia commented on the pull reque
Github user tedxia commented on the pull request:
https://github.com/apache/storm/pull/639#issuecomment-122199889
Yes we should use client.status(), and I am sorry for this error, I will
add new patch to fix this.
@caofangkun Will you have a look at Client, once client's stat
72 matches
Mail list logo
