We just issued a PR about FLINK-1827 (
https://github.com/apache/flink/pull/1915) that improves test stability
except for the ml library that has still some problem to solve..
On 21 Apr 2016 23:59, "Fabian Hueske" wrote:
> Hi Sourigna,
>
> thanks for contributing!
>
> Unrelated test failures are
Hi Sourigna,
thanks for contributing!
Unrelated test failures are not a problem. We have some issues with build
stability on Travis.
We know which tests are failing from time to time and run the tests again
before merging.
Thanks
2016-04-21 23:18 GMT+02:00 Sourigna Phetsarath :
> All:
>
> I cr
All:
I created this pull request and it failed on the flink-ml module that I
didn't touch. What are next steps?
https://github.com/apache/flink/pull/1920
Thank you for any help.
--
*Gna Phetsarath*System Architect // AOL Platforms // Data Services //
Applied Research Chapter
770 Broadway, 5
Chenguang He created FLINK-3802:
---
Summary: Add Very Fast Reservoir Sampling
Key: FLINK-3802
URL: https://issues.apache.org/jira/browse/FLINK-3802
Project: Flink
Issue Type: Improvement
This vote has passed with 3 binding +1 votes. Thanks to everyone who
contributed and tested the release candidate.
+1s:
Robert Metzger (binding)
Fabian Hueske (binding)
Aljoscha Krettek (binding)
There are no 0s or -1s.
I'll finalize and package this release asap.
On Thu, Apr 21, 2016 at 7:04 P
Ted Yu created FLINK-3801:
-
Summary: Upgrade Joda-Time library to 2.9.3
Key: FLINK-3801
URL: https://issues.apache.org/jira/browse/FLINK-3801
Project: Flink
Issue Type: Improvement
Report
Hi,
in the 1.0.2 release thread we started already collecting issues for the
next bugfix release.
I think it would be helpful to keep the two discussions separate and start
a new thread for the 1.0.3 rel.
Fixes to be included:
https://issues.apache.org/jira/browse/FLINK-3790
https://issues.apach
I started a new thread for the 1.0.3 release to collect all the JIRAs there.
On Thu, Apr 21, 2016 at 6:52 PM, Maximilian Michels wrote:
> This is also fairly critical for Scala shell users:
> https://issues.apache.org/jira/browse/FLINK-3701
>
> On Thu, Apr 21, 2016 at 5:53 PM, Till Rohrmann
> w
This is also fairly critical for Scala shell users:
https://issues.apache.org/jira/browse/FLINK-3701
On Thu, Apr 21, 2016 at 5:53 PM, Till Rohrmann wrote:
> I found another critical issue for the next bug fix release:
> https://issues.apache.org/jira/browse/FLINK-3800
>
> On Thu, Apr 21, 2016 at
Vasia and I are looking for additional feedback on FLINK-3772. This ticket
[0] and PR [1] provides a set of graph algorithms which compute and store
the degree for vertices and edges.
Degree annotation is a basic component of many algorithms. For example,
PageRank requires the vertex out-degree to
Vasia and I are looking for additional feedback on FLINK-3771. This ticket
[0] and PR [1] provides methods for translating the type or value of graph
labels, vertex values, and edge values. My use cases are provided in JIRA,
but I think users will find many more.
Translators compose well with grap
I found another critical issue for the next bug fix release:
https://issues.apache.org/jira/browse/FLINK-3800
On Thu, Apr 21, 2016 at 11:03 AM, Aljoscha Krettek
wrote:
> +1, the releases are very lightweight if we only add few commits
>
> On Thu, 21 Apr 2016 at 10:48 Gyula Fóra wrote:
>
> > +1
Hi,
yes, I see operators of this style as very much an internal thing. You are
probably talking about use cases for OneInputOperator and TwoInputOperator
where users have a very specific need and require access the the low-level
details such as watermarks, state and timers to get stuff done. Maybe
Till Rohrmann created FLINK-3800:
Summary: ExecutionGraphs can become orphans
Key: FLINK-3800
URL: https://issues.apache.org/jira/browse/FLINK-3800
Project: Flink
Issue Type: Bug
Co
Hey,
Some initial feedback from side:
I think this a very important problem to deal with as a lot of applications
depend on it. I like the proposed runtime model and that is probably the
good way to handle this task, it is very clean what is happening.
My main concern is how to handle this from
Hi Team,
I'm currently thinking about how we can bring the broadcast set/broadcast
input feature form the DataSet API to the DataStream API. I think this
would be a valuable addition since it would enable use cases that join
streams with constant (or slowly changing) side information.
For this pur
Greg Hogan created FLINK-3799:
-
Summary: Graph checksum should execute single job
Key: FLINK-3799
URL: https://issues.apache.org/jira/browse/FLINK-3799
Project: Flink
Issue Type: Improvement
Hi Till,
It works as expected, thanks!
Andrea
2016-04-19 15:25 GMT+02:00 Till Rohrmann :
> Hi Andrea,
>
> I think your problem should be fixed with the PRs [1,2]. I've tested it
> locally on my yarn cluster and it worked.
>
> [1] https://github.com/apache/flink/pull/1904
> [2] https://github.co
Hey,
I have encountered a strange error in the kafka consumer. This only
happened once in my local machine so far but just wanted to let you know.
java.lang.Exception: The periodic offset committer encountered an error:
org/apache/flink/shaded/org/apache/curator/HandleHolder$2
at
com.king.rbea.fl
+1, the releases are very lightweight if we only add few commits
On Thu, 21 Apr 2016 at 10:48 Gyula Fóra wrote:
> +1 from me as well :)
>
> Till Rohrmann ezt írta (időpont: 2016. ápr. 21.,
> Cs,
> 10:34):
>
> > +1 for Robert's proposal.
> >
> > On Thu, Apr 21, 2016 at 9:30 AM, Robert Metzger
>
+1 from me as well :)
Till Rohrmann ezt írta (időpont: 2016. ápr. 21., Cs,
10:34):
> +1 for Robert's proposal.
>
> On Thu, Apr 21, 2016 at 9:30 AM, Robert Metzger
> wrote:
>
> > Hi,
> >
> > I'm in favor of bringing this RC out as Flink 1.0.2 for the following
> > reasons:
> > - The vote is over
+1 for Robert's proposal.
On Thu, Apr 21, 2016 at 9:30 AM, Robert Metzger wrote:
> Hi,
>
> I'm in favor of bringing this RC out as Flink 1.0.2 for the following
> reasons:
> - The vote is over today and we have 3 +1 votes
> - At least one production user (Konstantin) urgently needs a fix contain
Hi,
I'm in favor of bringing this RC out as Flink 1.0.2 for the following
reasons:
- The vote is over today and we have 3 +1 votes
- At least one production user (Konstantin) urgently needs a fix contained
in the RC (It contains more critical fixes from other prod users as well)
- Gyula has a work
23 matches
Mail list logo
