Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/1237#issuecomment-162654340
You are right of course and I'm sorry I didn't put in the required time
earlier.
Your are also right about the Calcite thing. If we decide to use calcite
and have the Table API basically as another fronted to generate SQL plans then
the Table API optimization part can be very thin. In that case we would also
not need the Predicate push down as implemented as part of this PR, though, and
can keep it lean and simple.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
