Github user sachingoel0101 commented on the pull request:
https://github.com/apache/flink/pull/966#issuecomment-128230692
I'm inclined towards the Abstract class too. If we're saying something is
context aware, we better provide access to it IMO. It doesn't make sense to ask
the user to write it themselves and guarantee that we'd just call the relevant
methods at runtime.
As for the names, wouldn't it be better to maintain consistency in naming?
All the * rich * functions are named `RichFunctions`, which is why I decided to
name these `RichFormat`s too. I do agree though. The IO formats are already
pretty * rich * in the sense that they allow the user to control everything
that happens at runtime.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
