Github user nkronenfeld commented on the pull request:

    https://github.com/apache/spark/pull/5565#issuecomment-94519103
  
    @srowen - If I understand your question, you're asking why we can't take 
our application, written for an RDD, and just put the whole thing inside a call 
to dstream.foreachRDD... I'm not ignoring it, I'm trying to figure out what 
would happen if we did that, and that might take a bit.
    
    Regarding your answer to @harishreedharan, I would say, of course we don't 
have to - but we really should have from the start.  To have two nearly, but 
not quite, identical APIs is confusing, and encourages inconsistency; having a 
common interface enforces that the methods in both mean the same thing now, 
change together in the future, and are consistent.


---
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

Reply via email to