Github user hmcl commented on the issue:
https://github.com/apache/storm/pull/1924
@srdo @HeartSaVioR I will do the last pass on this first thing in the
morning such that we can merge this in.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user cpuchakayaka commented on the issue:
https://github.com/apache/storm/pull/250
@RaghavendraNandagopal any chance u can reopen the pull request, would love
to have this functionality?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user satishd commented on the issue:
https://github.com/apache/storm/pull/2021
+1, travis test failures does not seem to be related to this change.
---
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
Hi Alexandre,
If you don't mind me asking, what is your process for creating your topology
jars?
Once a release is approved, all artifacts are available in the Maven mirrors
and can be downloaded with a curl command or a browser. You will still have to
deal with transient dependencies, which
I forgot to say thank you for the feedback on the release candidate!
Feedback, positive or negative, is always welcome and a great way to get
involved in the project.
-Taylor
> On Mar 21, 2017, at 6:37 PM, P. Taylor Goetz wrote:
>
> Hi Alexandre,
>
> If you don't mind me
GitHub user djudd-stripe opened a pull request:
https://github.com/apache/storm/pull/2023
STORM-2429: Properly validate supervisor.scheduler.meta
https://issues.apache.org/jira/browse/STORM-2429
You can merge this pull request into a Git repository by running:
$ git pull
Hello,
Unlike with Storm 1.1.0 RC2, storm-kafka-1.1.0.jar is missing from
/external/storm-kafka
This directory only contains README.md, which doesn't explains how to get
storm-kafka-1.1.0.jar.
Would it be possible to have some detailled instructions on how to build
storm-kafka-1.1.0.jar
This is a call to vote on releasing Apache Storm 1.1.0 (rc3)
Full list of changes in this release:
https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=CHANGELOG.md;h=68fbab3c4f91359bd397d93a157830542839b002;hb=e40d213de7067f7d3aa4d4992b81890d8ed6ff31
The tag/commit to be voted
Github user srdo commented on the issue:
https://github.com/apache/storm/pull/1924
@HeartSaVioR I think as long as the spout can seek to the tuples it needs
to retry instead of seeking to the committed offset, all of the minor issues I
could think of are resolved.
---
If your
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1924
@hmcl
I think @srdo addressed your last review comments. Could you finish the
review?
Please let me know if there're some points we need to discuss or resolve,
so that we can address
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/2008
---
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 user asfgit closed the pull request at:
https://github.com/apache/storm/pull/2020
---
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 user srdo opened a pull request:
https://github.com/apache/storm/pull/2022
STORM-2343: New Kafka spout can stop emitting tuples if more than maxâ¦
â¦UncommittedOffsets tuples fail at once
1.x version of https://github.com/apache/storm/pull/1924
You can merge this
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/1999
---
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
14 matches
Mail list logo