[
https://issues.apache.org/jira/browse/SPARK-13877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15195873#comment-15195873
]
Mark Grover commented on SPARK-13877:
-------------------------------------
I am in support of taking the kafka integration out as well. However, in my
mind, we should figure out the answer to the following questions before we do
(some of these have already been aptly pointed out by Cody and Sean):
* Where will the code repo be located?
* Who would have access to commit code?
* How do we track issues there? Github Issues/PRs?
* Whose infrastructure would the test jobs run on?
* Where would the artifacts be released? Probably not on apache.org/dist. If
not there, then where?
> Consider removing Kafka modules from Spark / Spark Streaming
> ------------------------------------------------------------
>
> Key: SPARK-13877
> URL: https://issues.apache.org/jira/browse/SPARK-13877
> Project: Spark
> Issue Type: Sub-task
> Components: Spark Core, Streaming
> Affects Versions: 1.6.1
> Reporter: Hari Shreedharan
>
> Based on the discussion the PR for SPARK-13843
> ([here|https://github.com/apache/spark/pull/11672#issuecomment-196553283]),
> we should consider moving the Kafka modules out of Spark as well.
> Providing newer functionality (like security) has become painful while
> maintaining compatibility with older versions of Kafka. Moving this out
> allows more flexibility, allowing users to mix and match Kafka and Spark
> versions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
