Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/3798#issuecomment-72777123
Ohh I meant createStream --> createDirectStream. I would have preferred
something like createReceiverLessStream but thats a mouthful. I think "direct"
is something that comes close without being a mouthful. Had not occurred to me
until Patrick suggested it.
And the underlying assumptions, I confess are not super concrete.
Somethings like binary compatiblity issues (ex, do not use scala traits with
implemented methods) are fairly concrete, where as things about API elegance
(e.g. rdd.asInstanceOf[KafkaRDD] vs rdd.asInstanceOf[HasOffsetRanges]) are a
little fuzzy and opinions vary from person to person. Often what seems
intuitive to me is not intuitive to someone else, even within the key
committers like Patrick, Michael, Matei, etc. We usually argue about this in
design docs, get as many eyeballs as possible, and try to reach a consensus.
Its is indeed a bit fuzzy, but its all towards making the API that we *think*
will be the best for the developers.
---
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.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
