[
https://issues.apache.org/jira/browse/HBASE-16179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15552311#comment-15552311
]
Sean Busbey commented on HBASE-16179:
-------------------------------------
1) Problems with other in-flight tickets aren't relevant to issues with this one
2) this change impacts users down stream of us. AFAIK, a downstream user who
wants to run our module on Spark 2.0 needs different jars than someone who
wants to run our module on Spark 1.6.
3) If you believe the current Hadoop 3 profile requires us to do multiple build
steps to generate different convenience binaries, please do file a jira about
it or comment on where ever that work is happening. If our current use of
hadoop is only source compatible and not binary compatible for use with
supported Hadoop 2s and supported Hadoop 3s, that's a problem. (Though AFAIK we
haven't officially adopted a position of supporting Hadoop 3.)
> Fix compilation errors when building hbase-spark against Spark 2.0
> ------------------------------------------------------------------
>
> Key: HBASE-16179
> URL: https://issues.apache.org/jira/browse/HBASE-16179
> Project: HBase
> Issue Type: Bug
> Components: spark
> Reporter: Ted Yu
> Assignee: Ted Yu
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: 16179.v0.txt, 16179.v1.txt, 16179.v1.txt, 16179.v10.txt,
> 16179.v11.txt, 16179.v4.txt, 16179.v5.txt, 16179.v7.txt, 16179.v8.txt,
> 16179.v9.txt
>
>
> I tried building hbase-spark module against Spark-2.0 snapshot and got the
> following compilation errors:
> http://pastebin.com/bg3w247a
> Some Spark classes such as DataTypeParser and Logging are no longer
> accessible to downstream projects.
> hbase-spark module should not depend on such classes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
