Yes, that was my fault. I'm used to auto reply-all on my desktop machine,
but my phone just did a simple reply.
Sorry for the confusion,
Fabian
2016-06-29 19:24 GMT+02:00 Ovidiu-Cristian MARCU <
ovidiu-cristian.ma...@inria.fr>:
> Thank you, Aljoscha!
> I received a similar update from Fabian, o
Thank you, Aljoscha!
I received a similar update from Fabian, only now I see the user list was not
in CC.
Fabian::The optimizer hasn’t been touched (except for bugfixes and new
operators) for quite some time.
These limitations are still present and I don’t expect them to be removed
anytime soon
Hi,
I think this document is still up-to-date since not much was done in these
parts of the code for the 1.0 release and after that.
Maybe Timo can give some insights into what optimizations are done in the
Table API/SQL that will be be released in an updated version in 1.1.
Cheers,
Aljoscha
+Ti
Hi,
The optimizer internals described in this document [1] are probably not
up-to-date.
Can you please confirm if this is still valid:
“The following optimizations are not performed
Join reordering (or operator reordering in general): Joins / Filters / Reducers
are not re-ordered in Flink. This
