I would like to include the fixes for the Table API: RowSerializer supports null values, Aggregations properly deal with null values.
What do you think? On Mon, 15 Jun 2015 at 17:31 Aljoscha Krettek <[email protected]> wrote: > I created this to help with release testing: > https://github.com/aljoscha/FliRTT > > You just start your cluster and then point the tool to the Flink > directory. It will then run all the examples with both builtin data and > external data. > > On Mon, 15 Jun 2015 at 17:15 Maximilian Michels <[email protected]> wrote: > >> Hmm. Might be interesting to check out whether this is a regression from >> rc1 to rc2. In any case, it is a serious release blocker and we need to >> fix >> it. >> >> On Mon, Jun 15, 2015 at 5:04 PM, Till Rohrmann <[email protected]> >> wrote: >> >> > I might have found another release blocker. While running some cluster >> > tests I also tried to run the `ConnectedComponents` example. However, >> > sometimes the example couldn't be executed because the scheduler could >> not >> > schedule co-located tasks, `NoResourceAvailableException`, even though >> it >> > should have had enough slots. It also happened on a fresh Flink >> cluster. I >> > opened a corresponding JIRA issue [1]. >> > >> > The error seems to be similar to the error reported in FLINK-1952 [2]. >> > However, I thought that this problem was already fixed. But maybe the >> error >> > was reintroduced by the latest change to the scheduler, FLINK-2183 [3, >> 4]. >> > >> > [1] https://issues.apache.org/jira/browse/FLINK-2225 >> > [2] https://issues.apache.org/jira/browse/FLINK-1952 >> > [3] https://issues.apache.org/jira/browse/FLINK-2183 >> > [4] >> > >> > >> https://github.com/apache/flink/commit/e966a0dd1c9f35ba6cb0ff4e09205c411fc4585d >> > >> > On Mon, Jun 15, 2015 at 3:45 PM Ufuk Celebi <[email protected]> wrote: >> > >> > > Please continue the discussion in the issue Aljoscha opened: >> > > https://issues.apache.org/jira/browse/FLINK-2221 >> > > >> > > I think it is better to only point to issues in this mail thread. >> > > Otherwise the discussions are very hard to follow. >> > > >> > > >> > >> >
