[GitHub] storm pull request: Fix bug related to error handling in js multil...

GitHub user anyatch opened a pull request: https://github.com/apache/storm/pull/341 Fix bug related to error handling in js multilang implementation You can merge this pull request into a Git repository by running: $ git pull https://github.com/forter/storm

[jira] [Commented] (STORM-585) Performance issue in none grouping

[ https://issues.apache.org/jira/browse/STORM-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14237918#comment-14237918 ] ASF GitHub Bot commented on STORM-585: -- GitHub user fmazoyer opened a pull request:

[GitHub] storm pull request: Storm 585

Github user fmazoyer closed the pull request at: https://github.com/apache/storm/pull/342 --- 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-585) Performance issue in none grouping

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

[GitHub] storm pull request: [STORM-391] KafkaSpout to await for the topic

Github user lazyval commented on the pull request: https://github.com/apache/storm/pull/338#issuecomment-66127049 Guys, how about using curator api for this particular problem and raising new ticket *Kafka spout should rely on kafka APIs, rather than perform low-level manipulations

[jira] [Commented] (STORM-391) KafkaSpout to await for the topic

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

[jira] [Updated] (STORM-340) Add topology submission REST API and UI button

[ https://issues.apache.org/jira/browse/STORM-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] shanyu zhao updated STORM-340: -- Description: STORM-205 added REST API to Storm, but these API are only used to monitor/manage a

Trident Documentation

Hello all,Is there any way to improve the Trident documentation? We are working on developing a trident topology and many times there is not enough documentation to figure out the APIs. For example, Snapshottable interface.  What is the process for adding the documents. ThanksNikhil

Re: Trident Documentation

Storm documentation has moved recently to github https://github.com/apache/storm/tree/master/docs. You could add documentation under that or you could just add java docs to the class and submit a pull request. Thanks Parth On Dec 8, 2014, at 1:31 PM, Nikhil Singh nsingh.u...@yahoo.com.INVALID

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

Github user Parth-Brahmbhatt commented on a diff in the pull request: https://github.com/apache/storm/pull/339#discussion_r21495048 --- Diff: external/storm-kafka/src/jvm/storm/kafka/UpdateOffsetException.java --- @@ -17,6 +17,9 @@ */ package storm.kafka;

[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=14238636#comment-14238636 ] ASF GitHub Bot commented on STORM-586: -- Github user Parth-Brahmbhatt commented on a

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

GitHub user Parth-Brahmbhatt reopened a pull request: https://github.com/apache/storm/pull/339 STORM-586: TridentKafkaEmitter should catch updateOffsetException. You can merge this pull request into a Git repository by running: $ git pull

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

Github user Parth-Brahmbhatt commented on the pull request: https://github.com/apache/storm/pull/339#issuecomment-66206449 I also tested this locally and it works fine for OpaqueTridentSpout. The TransactionalSpout tries to reemit a batch and when the offset is out of range there is

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

Github user Parth-Brahmbhatt 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

[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=14238637#comment-14238637 ] ASF GitHub Bot commented on STORM-586: -- Github user Parth-Brahmbhatt commented on the

[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=14238638#comment-14238638 ] ASF GitHub Bot commented on STORM-586: -- Github user Parth-Brahmbhatt closed the pull