[
https://issues.apache.org/jira/browse/STORM-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14238639#comment-14238639
]
ASF GitHub Bot commented on STORM-586:
--
GitHub user Parth-Brahmbhatt reopened a pull r
[
https://issues.apache.org/jira/browse/STORM-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14238637#comment-14238637
]
ASF GitHub Bot commented on STORM-586:
--
Github user Parth-Brahmbhatt commented on the
[
https://issues.apache.org/jira/browse/STORM-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14238638#comment-14238638
]
ASF GitHub Bot commented on STORM-586:
--
Github user Parth-Brahmbhatt closed the pull r
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 featur
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 https://github.com/Parth-Brahmbhatt/i
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 n
[
https://issues.apache.org/jira/browse/STORM-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14238636#comment-14238636
]
ASF GitHub Bot commented on STORM-586:
--
Github user Parth-Brahmbhatt commented on a di
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;
-publ
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 wrote:
> Hello all,Is there
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
[
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 topology
[
https://issues.apache.org/jira/browse/STORM-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14237930#comment-14237930
]
ASF GitHub Bot commented on STORM-391:
--
Github user lazyval commented on the pull requ
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 wi
[
https://issues.apache.org/jira/browse/STORM-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14237927#comment-14237927
]
ASF GitHub Bot commented on STORM-585:
--
Github user fmazoyer closed the pull request a
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 ena
[
https://issues.apache.org/jira/browse/STORM-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14237918#comment-14237918
]
ASF GitHub Bot commented on STORM-585:
--
GitHub user fmazoyer opened a pull request:
GitHub user fmazoyer opened a pull request:
https://github.com/apache/storm/pull/342
Storm 585
Hello, I just fixed the issue I found :
https://issues.apache.org/jira/browse/STORM-585.
I pushed it to my fork, into branch STORM-585.
As this is my first pull request from my for
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 nodejs-error-handli
[
https://issues.apache.org/jira/browse/STORM-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14237774#comment-14237774
]
ASF GitHub Bot commented on STORM-583:
--
Github user lazyval commented on the pull requ
Github user lazyval commented on the pull request:
https://github.com/apache/storm/pull/336#issuecomment-66102829
@shanyu it might be a good idea to put *STORM-583* in this PR title, so
jira's github bot and people could relate issue and PR to each other.
---
If your project is set
20 matches
Mail list logo
