[
https://issues.apache.org/jira/browse/SPARK-20287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15971893#comment-15971893
]
Stephane Maarek commented on SPARK-20287:
-
[~c...@koeninger.org] It makes sense. I didn't
[
https://issues.apache.org/jira/browse/SPARK-20287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966973#comment-15966973
]
Stephane Maarek commented on SPARK-20287:
-
[~c...@koeninger.org]
How about using the subscribe
[
https://issues.apache.org/jira/browse/SPARK-20287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15966180#comment-15966180
]
Cody Koeninger commented on SPARK-20287:
The issue here is that the underlying new Kafka consumer
[
https://issues.apache.org/jira/browse/SPARK-20287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15963939#comment-15963939
]
Stephane Maarek commented on SPARK-20287:
-
The other issue I can see is the coordinator work that
[
https://issues.apache.org/jira/browse/SPARK-20287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15963938#comment-15963938
]
Stephane Maarek commented on SPARK-20287:
-
[~srowen] those are good points. In the case of 100
[
https://issues.apache.org/jira/browse/SPARK-20287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15963920#comment-15963920
]
Sean Owen commented on SPARK-20287:
---
Spark has a different execution model though where it does want to
