flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephan Ewen <se...@apache.org>
Subject Re: Different Test Outcome Java 7/8
Date Mon, 01 Sep 2014 11:56:40 GMT

The optimizer pushes certain strategies down before the map operators. That
is correct, but it would be good to have a bias to not do that unless it
yields a clear advantage.

For that case, the simplest fix would be to give the mapper a selectivity
smaller than one. That should do it.


On Mon, Sep 1, 2014 at 1:47 PM, Sebastian Kunert <skunert49@gmail.com>

> Hi,
> I have different plans for the DOPChangeTest in java 7 and 8. Here are the
> two plans that are generated:
> Java 7: http://pastebin.com/krzF0gmJ
> Java 8: http://pastebin.com/a6TuBjzB
> The plans are equivalent and both okay. The question is how to deal with
> this in a testcase when we have to expect a specific plan. The problem
> arises in this pull request:
> https://github.com/apache/incubator-flink/pull/83
> Sebastian

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message