Github user zentol commented on the pull request:
https://github.com/apache/incubator-flink/pull/202#issuecomment-63859374
damn it Robert, why are you making me rethink my PR? :(
i see your point. Maybe I'm oversimplifying things, but my conclusion is
that if we want to prevent people from dismissing the Python API completely due
to premature assessments we end up in a catch-up game we cant win. Next time
it's gonna be missing feature X that's causing it, and after that is fixed that
we may end up talking about feature Y or yet again about performance.
My other major gripe is that there are things that people could work on
while we fix the performance. The PlanBinding stuff is completely irrelevant to
performance. So is Windows support (which surprisingly enough is not just about
paths O.o). I can surely find more things if i wanted to.
these things will fall flat when we don't merge it, since creating issues
(and resolving them), while the code is not in the main project seems a bit
iffy.
---
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.
---
