[
https://issues.apache.org/jira/browse/HBASE-16179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15553309#comment-15553309
]
Jonathan Hsieh commented on HBASE-16179:
----------------------------------------
[~tedyu], for the hadoop 3 changes, even though there are two profiles, there
is only one set of code and one set of hbase-server binaries that could be used
against either hadoop 2.x or hadoop 3.x. The profiles simplify unit testing
does not require separate binaries to run against hadoop 2 or hadoop3.
The discussion here is about having two different modules and binaries -- one
for spark 1.x and one for spark 2.x. If you can you make it one binary the two
cases are similar. If you have to make different binaries for each version, it
is very different from a release manager's point of view.
> 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)
