[jira] [Commented] (STORM-605) Attempting to call unbound fn during bolt prepare

[ https://issues.apache.org/jira/browse/STORM-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14265888#comment-14265888 ] Li Chaomo commented on STORM-605: - i'm the same as you. we use clojureDSL under storm

[GitHub] storm pull request: STORM-248 STORM-322 proposal for fix

Github user fmazoyer commented on the pull request: https://github.com/apache/storm/pull/353#issuecomment-68863466 Rebased and resolved conflicts from upstream/master. Unfortunately, it also took two files I did not intend to pull: changelog.md and SequenceFormat.java. Sorry

[GitHub] storm pull request: Storm 616 : Storm-jdbc connector.

Github user harshach commented on the pull request: https://github.com/apache/storm/pull/372#issuecomment-68871971 @Parth-Brahmbhatt looks like you might have unintended commit as part of this PR. STORM-586: TridentKafkaEmitter should catch updateOffsetException. --- If your

[GitHub] storm pull request: [STORM-611] Remove extra breaks

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/367 --- 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

[GitHub] storm pull request: [STORM-610] Check the return value of fts_clos...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/366 --- 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

[jira] [Resolved] (STORM-611) worker-launcher.c contains extra breaks

[ https://issues.apache.org/jira/browse/STORM-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans resolved STORM-611. --- Resolution: Fixed Fix Version/s: 0.10.0 Assignee: Muneyuki Noguchi

[jira] [Created] (STORM-617) In Storm secure mode re-deploying trident topology causes zookeeper ACL issue

Sriharsha Chintalapani created STORM-617: Summary: In Storm secure mode re-deploying trident topology causes zookeeper ACL issue Key: STORM-617 URL: https://issues.apache.org/jira/browse/STORM-617

[jira] [Resolved] (STORM-599) UI is slow due to fetching heartbeats from ZK

[ https://issues.apache.org/jira/browse/STORM-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans resolved STORM-599. --- Resolution: Fixed Fix Version/s: 0.10.0 Thanks [~dagit], I merged this into

[GitHub] storm pull request: [STORM-410] Add groups support to log-viewer

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/317 --- 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

[jira] [Resolved] (STORM-444) (Security) Add AutoHDFS like credential fetching for HBase

[ https://issues.apache.org/jira/browse/STORM-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans resolved STORM-444. --- Resolution: Fixed Fix Version/s: 0.10.0 Assignee: Parth Brahmbhatt

[GitHub] storm pull request: STORM-248 STORM-322 are fixed and upmerged

Github user revans2 commented on the pull request: https://github.com/apache/storm/pull/373#issuecomment-68935435 One minor comment, but other then that it looks good. --- 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] storm pull request: [STORM-442] multilang ShellBolt/ShellSpout die...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/305 --- 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

[jira] [Resolved] (STORM-410) (Security) add groups support to logviewer

[ https://issues.apache.org/jira/browse/STORM-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans resolved STORM-410. --- Resolution: Fixed Fix Version/s: 0.10.0 Assignee: Robert Joseph Evans

[jira] [Commented] (STORM-410) (Security) add groups support to logviewer

[ https://issues.apache.org/jira/browse/STORM-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14266849#comment-14266849 ] ASF GitHub Bot commented on STORM-410: -- Github user asfgit closed the pull request at:

[jira] [Resolved] (STORM-610) worker-launcher doesn't check return value of fts_close while setting up a directory

[ https://issues.apache.org/jira/browse/STORM-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans resolved STORM-610. --- Resolution: Fixed Fix Version/s: 0.10.0 Assignee: Muneyuki Noguchi

[GitHub] storm pull request: STORM-248 STORM-322 are fixed and upmerged

Github user revans2 commented on a diff in the pull request: https://github.com/apache/storm/pull/373#discussion_r22552440 --- Diff: bin/storm --- @@ -74,7 +74,8 @@ if (not os.path.isfile(os.path.join(USER_CONF_DIR, storm.yaml))): STORM_RELEASE_DIR = os.path.join(STORM_DIR,

[jira] [Commented] (STORM-442) multilang ShellBolt/ShellSpout die() can be hang when Exception happened

[ https://issues.apache.org/jira/browse/STORM-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14266793#comment-14266793 ] ASF GitHub Bot commented on STORM-442: -- Github user revans2 commented on the pull

[GitHub] storm pull request: [STORM-442] multilang ShellBolt/ShellSpout die...

Github user revans2 commented on the pull request: https://github.com/apache/storm/pull/305#issuecomment-68936183 No other comments in the past two weeks so I am going to check this in. --- If your project is set up for it, you can reply to this email and have your reply appear on

[jira] [Commented] (STORM-442) multilang ShellBolt/ShellSpout die() can be hang when Exception happened

[ https://issues.apache.org/jira/browse/STORM-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14266804#comment-14266804 ] ASF GitHub Bot commented on STORM-442: -- Github user asfgit closed the pull request at:

[jira] [Commented] (STORM-599) UI is slow due to fetching heartbeats from ZK

[ https://issues.apache.org/jira/browse/STORM-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14266832#comment-14266832 ] ASF GitHub Bot commented on STORM-599: -- Github user asfgit closed the pull request at:

[GitHub] storm pull request: [STORM-599] Use use nimbus's cached heartbeats...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/356 --- 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

[GitHub] storm pull request: Storm-616 : Storm-jdbc connector.

GitHub user Parth-Brahmbhatt opened a pull request: https://github.com/apache/storm/pull/374 Storm-616 : Storm-jdbc connector. You can merge this pull request into a Git repository by running: $ git pull https://github.com/Parth-Brahmbhatt/incubator-storm STORM-616

[GitHub] storm pull request: Storm-444: Moving AutoHDFS to storm-hdfs and A...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/344 --- 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

[jira] [Commented] (STORM-248) cluster.xml location is hardcoded for workers.

[ https://issues.apache.org/jira/browse/STORM-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14266771#comment-14266771 ] ASF GitHub Bot commented on STORM-248: -- Github user revans2 commented on a diff in the

[GitHub] storm pull request: STORM-248 STORM-322 are fixed and upmerged

GitHub user fmazoyer opened a pull request: https://github.com/apache/storm/pull/373 STORM-248 STORM-322 are fixed and upmerged Details are in JIRA https://issues.apache.org/jira/browse/STORM-248. As a collateral benefit, this also addresses JIRA

[jira] [Resolved] (STORM-612) configure.ac sets the google groups account as a contact address

[ https://issues.apache.org/jira/browse/STORM-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans resolved STORM-612. --- Resolution: Fixed Fix Version/s: 0.10.0 Assignee: Muneyuki Noguchi

[jira] [Commented] (STORM-605) Attempting to call unbound fn during bolt prepare

[ https://issues.apache.org/jira/browse/STORM-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14266373#comment-14266373 ] Sriharsha Chintalapani commented on STORM-605: -- [~phyce] [~newday1] If

[GitHub] storm pull request: STORM-613: Fix wrong getOffset return value

Github user revans2 commented on the pull request: https://github.com/apache/storm/pull/369#issuecomment-68886875 +1 looks fine 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

[jira] [Commented] (STORM-586) Trident kafka spout fails instead of updating offset when kafka offset is out of range.

[ https://issues.apache.org/jira/browse/STORM-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14266358#comment-14266358 ] Sriharsha Chintalapani commented on STORM-586: -- PR merged into master. Thanks.

[jira] [Commented] (STORM-586) Trident kafka spout fails instead of updating offset when kafka offset is out of range.

[ https://issues.apache.org/jira/browse/STORM-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14266357#comment-14266357 ] ASF GitHub Bot commented on STORM-586: -- Github user asfgit closed the pull request at:

[GitHub] storm pull request: Storm 616 : Storm-jdbc connector.

Github user harshach commented on a diff in the pull request: https://github.com/apache/storm/pull/372#discussion_r22536766 --- Diff: external/storm-jdbc/README.md --- @@ -0,0 +1,117 @@ +#Storm HBase + +Storm/Trident integration for JDBC. + +## Usage +The

[GitHub] storm pull request: [STORM-612] Update the contact address in conf...

Github user revans2 commented on the pull request: https://github.com/apache/storm/pull/368#issuecomment-6973 +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

[jira] [Resolved] (STORM-613) Fix wrong getOffset return value

[ https://issues.apache.org/jira/browse/STORM-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Joseph Evans resolved STORM-613. --- Resolution: Fixed Fix Version/s: 0.10.0 Thanks [~xiajun], I pulled this into

[GitHub] storm pull request: Storm 616 : Storm-jdbc connector.

Github user Parth-Brahmbhatt commented on the pull request: https://github.com/apache/storm/pull/372#issuecomment-68904233 * I noticed that and reverted those files to their state in master. * Added storm-jdbc to storm-core. * sorry about this, I accidently deleted it with

[jira] [Resolved] (STORM-586) Trident kafka spout fails instead of updating offset when kafka offset is out of range.

[ https://issues.apache.org/jira/browse/STORM-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriharsha Chintalapani resolved STORM-586. -- Resolution: Fixed Trident kafka spout fails instead of updating offset when

[GitHub] storm pull request: STORM-586: TridentKafkaEmitter should catch up...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/339 --- 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

[GitHub] storm pull request: Storm 616 : Storm-jdbc connector.

Github user harshach commented on the pull request: https://github.com/apache/storm/pull/372#issuecomment-68899213 @Parth-Brahmbhatt few things to note 1) add external/storm-jdbc to storm/pom.xml under modules 2) I didn't' find any dependency in storm-jdbc/pom.xml for