Github user mans2singh commented on the pull request:
https://github.com/apache/flink/pull/2031#issuecomment-222030024
Hi @rmetzger
Thanks for your advice/suggestions. I will try to answer your questions
below:
Regarding motivation for the connector - I started working with Flink late
last year and found it had some unique features (like streaming framework based
on events from the grounds up and flexibility of windowing options). I am
working through some real-time data flow use cases, where these capabilities
can stream line our processing pipelines. The integration with RethinkDB came
into play because from the dev perspective it is schema less, can ingest
streams/batch of data, has map/reduce functionality. From the ops/scaling
perspective it can be scaled/re-sharded in real-time without downtime. It can
also provide change streams for a table, or a document. IMHO, Flink and
Rethink complement each other for scalable, stream processing/analytics use
cases. So, I thought it might be good to contribute back to the open source
community and therefore the PR.
Regarding guidelines for code-contribution - I did go through the document
and I thought this PR would be in the same vein as the other streaming
connectors (kafka, etc), and complementing them. There was no new API, or
change in interfaces, and the code base is pretty light weight because
Flink/RethinkDB both make it easy to integrate. However, I did not realize that
it would be considered to a new feature and required a design review but
perhaps that was my oversight.
In any case, I really appreciate, the time you and your team took to review
the PR and advice me. Please let me know what's your recommendation on how I
should proceed.
Thanks, Mans
---
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.
---
