STORM-3217 and STORM-3221 have been fixed - +1 from me for 2.0 RC.
On Wed, Sep 12, 2018 at 10:01 AM Govind Menon wrote:
> Hi all,
>
> There are some regressions that I introduced as part of STORM-1311 which
> I'm working on as part of https://issues.apache.org/jira/browse/STORM-3217
> and
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/2828
---
GitHub user kishorvpatil opened a pull request:
https://github.com/apache/storm/pull/2831
STORM-3224: Fix FLUX YAML Viewer icon location/position on UI page
You can merge this pull request into a Git repository by running:
$ git pull
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/2827
---
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/2826
---
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/2825
---
GitHub user revans2 opened a pull request:
https://github.com/apache/storm/pull/2830
STORM-3223: Fix NPE on blacklisted rack
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/revans2/incubator-storm STORM-3223
Alternatively you
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/2824
---
At XenonStack we use Storm for building real-time data integration systems
and Enabling Predictive analysis
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/2829
@srdo is right. The reason is to enforce "max.spout.pending.limit", but the
concept is brought when backpressure is not in place. IMHO, the concept is the
thing we should drop whenever
Github user srdo commented on the issue:
https://github.com/apache/storm/pull/2829
@arunmahadevan I think the reason for only emitting one tuple at a time was
to let Storm enforce the max.spout.pending limit. Maybe it would be better to
accept some overflow in order to get the spout
11 matches
Mail list logo
