[jira] [Commented] (STORM-773) backtype.storm.transactional-test fails periodically with timeout

[ https://issues.apache.org/jira/browse/STORM-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14499072#comment-14499072 ] ASF GitHub Bot commented on STORM-773: -- Github user hustfxj commented on the pull requ

[jira] [Commented] (STORM-789) Enhance topology context sent to multi-lang bolts and spouts

[ https://issues.apache.org/jira/browse/STORM-789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14499098#comment-14499098 ] ASF GitHub Bot commented on STORM-789: -- Github user HeartSaVioR commented on the pull

[jira] [Commented] (STORM-773) backtype.storm.transactional-test fails periodically with timeout

[ https://issues.apache.org/jira/browse/STORM-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14499067#comment-14499067 ] Fang Xiaojian commented on STORM-773: - well done > backtype.storm.transactional-test f

[GitHub] storm pull request: STORM-790 Log "task is null" instead of let wo...

GitHub user HeartSaVioR opened a pull request: https://github.com/apache/storm/pull/527 STORM-790 Log "task is null" instead of let worker died when task is null in transfer-fn When task is null in transfer-fn, creating TaskMessage leads NPE. Please refer https://issues.apa

[jira] [Commented] (STORM-770) NullPointerException in consumeBatchToCursor

[ https://issues.apache.org/jira/browse/STORM-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14499225#comment-14499225 ] Jungtaek Lim commented on STORM-770: Before finding root cause of this issue, it would

[jira] [Commented] (STORM-770) NullPointerException in consumeBatchToCursor

[ https://issues.apache.org/jira/browse/STORM-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14499262#comment-14499262 ] Jungtaek Lim commented on STORM-770: STORM-790 addresses my comment - log strange behav

[jira] [Created] (STORM-790) Log "task id is null" instead of let worker died (NPE in consumeBatchToCursor)

Jungtaek Lim created STORM-790: -- Summary: Log "task id is null" instead of let worker died (NPE in consumeBatchToCursor) Key: STORM-790 URL: https://issues.apache.org/jira/browse/STORM-790 Project: Apach

[jira] [Updated] (STORM-790) Log "task id is null" instead of let worker died (NPE in consumeBatchToCursor)

[ https://issues.apache.org/jira/browse/STORM-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jungtaek Lim updated STORM-790: --- Affects Version/s: 0.11.0 0.9.4 0.10.0 > Log "task id is

[jira] [Commented] (STORM-790) Log "task id is null" instead of let worker died (NPE in consumeBatchToCursor)

[ https://issues.apache.org/jira/browse/STORM-790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14499260#comment-14499260 ] ASF GitHub Bot commented on STORM-790: -- GitHub user HeartSaVioR opened a pull request:

Question about Nimbus$Client

Dear all, the class backtype.storm.generated.Nimbus defines a nested class Nimbus$Cluster that offers the following two methods (both defined in Nimbus#Iface): > public StormTopology getTopology(String id) throws NotAliveException, > org.apache.thrift.TException; > public StormTopology

[GitHub] storm pull request: [STORM-789] Send more topology context to Mult...

Github user dan-blanchard commented on the pull request: https://github.com/apache/storm/pull/525#issuecomment-93991362 Hmm... actually, that output looks a little strange to me because "sources->grouping" and "stream->target->grouping" are empty. --- If your project is set up for it

[jira] [Commented] (STORM-789) Enhance topology context sent to multi-lang bolts and spouts

[ https://issues.apache.org/jira/browse/STORM-789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14499858#comment-14499858 ] ASF GitHub Bot commented on STORM-789: -- Github user dan-blanchard commented on the pul

[GitHub] storm pull request: [STORM-789] Send more topology context to Mult...

Github user dan-blanchard commented on the pull request: https://github.com/apache/storm/pull/525#issuecomment-93998284 I modified my local copy of storm.py to make it log the contexts its received and I noticed that `TesterSpout` gets: ```python {u'task->component':

[jira] [Commented] (STORM-789) Enhance topology context sent to multi-lang bolts and spouts

[ https://issues.apache.org/jira/browse/STORM-789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14499912#comment-14499912 ] ASF GitHub Bot commented on STORM-789: -- Github user dan-blanchard commented on the pul

[GitHub] storm pull request: [STORM-789] Send more topology context to Mult...

Github user HeartSaVioR commented on the pull request: https://github.com/apache/storm/pull/525#issuecomment-94002236 Oh, I confirmed that sources->grouping is missing from both Spout and Bolt. --- If your project is set up for it, you can reply to this email and have your reply appea

[jira] [Commented] (STORM-789) Enhance topology context sent to multi-lang bolts and spouts

[ https://issues.apache.org/jira/browse/STORM-789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14499951#comment-14499951 ] ASF GitHub Bot commented on STORM-789: -- Github user HeartSaVioR commented on the pull

[GitHub] storm pull request: [STORM-789] Send more topology context to Mult...

Github user dan-blanchard commented on the pull request: https://github.com/apache/storm/pull/525#issuecomment-94003059 Ok, I tweaked things a bit more and I realized there were a couple little issues with how I was building `sources->grouping`. As a result, I've had to make that a b

[jira] [Commented] (STORM-789) Enhance topology context sent to multi-lang bolts and spouts

[ https://issues.apache.org/jira/browse/STORM-789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14499962#comment-14499962 ] ASF GitHub Bot commented on STORM-789: -- Github user dan-blanchard commented on the pul

[GitHub] storm pull request: [STORM-643] KafkaUtils repeat fetch messages w...

Github user miguno commented on the pull request: https://github.com/apache/storm/pull/405#issuecomment-94007128 @vesense As [I said in the JIRA ticket](https://issues.apache.org/jira/browse/STORM-643?focusedCommentId=14494138&page=com.atlassian.jira.plugin.system.issuetabpanels:commen

[jira] [Commented] (STORM-643) KafkaUtils repeatedly fetches messages whose offset is out of range

[ https://issues.apache.org/jira/browse/STORM-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500018#comment-14500018 ] ASF GitHub Bot commented on STORM-643: -- Github user miguno commented on the pull reque

[GitHub] storm pull request: [STORM-789] Send more topology context to Mult...

Github user dan-blanchard commented on the pull request: https://github.com/apache/storm/pull/525#issuecomment-94009554 I think this is good to go now. It does indeed seem to be the case that for that test, there's a bolt that emits on a stream that no one is subscribing to. --- If

[jira] [Commented] (STORM-789) Enhance topology context sent to multi-lang bolts and spouts

[ https://issues.apache.org/jira/browse/STORM-789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500034#comment-14500034 ] ASF GitHub Bot commented on STORM-789: -- Github user dan-blanchard commented on the pul

Re: Question about Nimbus$Client

getTopology returns the compiled topology after nimbus has gotten its hands on it, so it has the ackers in it and the metrics consumers. getUserTopology returns the topology as the user submitted it.  - Bobby On Friday, April 17, 2015 4:24 AM, Matthias J. Sax wrote: Dear all, th

[jira] [Created] (STORM-791) Storm UI displays maps in the config incorrectly

Robert Joseph Evans created STORM-791: - Summary: Storm UI displays maps in the config incorrectly Key: STORM-791 URL: https://issues.apache.org/jira/browse/STORM-791 Project: Apache Storm

[GitHub] storm pull request: STORM-791: Storm UI displays maps in the confi...

GitHub user revans2 opened a pull request: https://github.com/apache/storm/pull/528 STORM-791: Storm UI displays maps in the config incorrectly You can merge this pull request into a Git repository by running: $ git pull https://github.com/revans2/incubator-storm STORM-791 Al

[jira] [Commented] (STORM-791) Storm UI displays maps in the config incorrectly

[ https://issues.apache.org/jira/browse/STORM-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500386#comment-14500386 ] ASF GitHub Bot commented on STORM-791: -- GitHub user revans2 opened a pull request:

[GitHub] storm pull request: STORM-791: Storm UI displays maps in the confi...

Github user revans2 commented on the pull request: https://github.com/apache/storm/pull/528#issuecomment-94048702  --- If your project is set up for it, you can reply to

[jira] [Commented] (STORM-791) Storm UI displays maps in the config incorrectly

[ https://issues.apache.org/jira/browse/STORM-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500399#comment-14500399 ] ASF GitHub Bot commented on STORM-791: -- Github user revans2 commented on the pull requ

[GitHub] storm pull request: STORM-791: Storm UI displays maps in the confi...

Github user knusbaum commented on the pull request: https://github.com/apache/storm/pull/528#issuecomment-94063949 +1 Super cool. --- 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 feat

[jira] [Commented] (STORM-791) Storm UI displays maps in the config incorrectly

[ https://issues.apache.org/jira/browse/STORM-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500570#comment-14500570 ] ASF GitHub Bot commented on STORM-791: -- Github user knusbaum commented on the pull req

[jira] [Commented] (STORM-512) KafkaBolt doesn't handle ticks properly

[ https://issues.apache.org/jira/browse/STORM-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500605#comment-14500605 ] ASF GitHub Bot commented on STORM-512: -- Github user nathanmarz commented on the pull r

[GitHub] storm pull request: STORM-512 KafkaBolt doesn't handle ticks prope...

Github user nathanmarz commented on the pull request: https://github.com/apache/storm/pull/275#issuecomment-94068063 I didn't get a notification that you were pinging me – but fwiw I'm +1 on it --- If your project is set up for it, you can reply to this email and have your reply a

[jira] [Assigned] (STORM-766) Supervisor summary should include the version.

[ https://issues.apache.org/jira/browse/STORM-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanket Chintapalli reassigned STORM-766: Assignee: Sanket Chintapalli (was: Parth Brahmbhatt) > Supervisor summary should in

[jira] [Commented] (STORM-766) Supervisor summary should include the version.

[ https://issues.apache.org/jira/browse/STORM-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500628#comment-14500628 ] Sanket Chintapalli commented on STORM-766: -- Hi Parth, I did change the code to dis

[jira] [Comment Edited] (STORM-766) Supervisor summary should include the version.

[ https://issues.apache.org/jira/browse/STORM-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500628#comment-14500628 ] Sanket Chintapalli edited comment on STORM-766 at 4/17/15 8:43 PM: --

[GitHub] storm pull request: JIRA STORM-766 (Include version info in the se...

GitHub user redsanket opened a pull request: https://github.com/apache/storm/pull/529 JIRA STORM-766 (Include version info in the service page) I have included the code to display the version info in the web-page. Let me know if you need any other requirement. You can merge this pu

[jira] [Commented] (STORM-766) Supervisor summary should include the version.

[ https://issues.apache.org/jira/browse/STORM-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500646#comment-14500646 ] ASF GitHub Bot commented on STORM-766: -- GitHub user redsanket opened a pull request:

[GitHub] storm pull request: JIRA STORM-766 (Include version info in the se...

Github user Parth-Brahmbhatt commented on a diff in the pull request: https://github.com/apache/storm/pull/529#discussion_r28629385 --- Diff: storm-core/src/clj/backtype/storm/converter.clj --- @@ -5,14 +5,17 @@ (:require [backtype.storm.daemon [common :as common]]))

[GitHub] storm pull request: JIRA STORM-766 (Include version info in the se...

Github user Parth-Brahmbhatt commented on the pull request: https://github.com/apache/storm/pull/529#issuecomment-94073243 All the generated files that really has no change other then the date should be removed from the PR. Looks good otherwise, will test once you remove the files.

[jira] [Commented] (STORM-766) Supervisor summary should include the version.

[ https://issues.apache.org/jira/browse/STORM-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500651#comment-14500651 ] ASF GitHub Bot commented on STORM-766: -- Github user Parth-Brahmbhatt commented on a di

[jira] [Commented] (STORM-766) Supervisor summary should include the version.

[ https://issues.apache.org/jira/browse/STORM-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14500653#comment-14500653 ] ASF GitHub Bot commented on STORM-766: -- Github user Parth-Brahmbhatt commented on the

Upgrading Storm to use Netty 4.0 or higher

Hi All, I am quite curious to know if there is any interest or activity around upgrading Storm to use Netty 4.0 or higher. From what I understand, Storm (at least till the 0.10.0 dev branch I checked out) still depends on Netty 3.x. and Netty 4.x is not compatible with 3.x code Link