[
https://issues.apache.org/jira/browse/SPARK-13877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15200079#comment-15200079
]
Mark Grover commented on SPARK-13877:
-------------------------------------
I am guessing this needs to be done before Spark 2.0 code freeze. Also, if we
are moving this to be outside of Spark, it's not a part of Apache Spark project
any more, so in my opinion, we should be updating the maven coordinates and
package names to be something like {{org.spark-packages.*}}. I am happy to
volunteer to make those changes, unless someone has objection.
But, I think it's a big enough change for our end users that we should have a
dev@ vote thread on this. Also, we need to come up with a who can commit code
to this external repo. All Spark committers seems like a safe choice to begin
with but could be expand later on. Thoughts?
> 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
