[
https://issues.apache.org/jira/browse/SPARK-20202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15953489#comment-15953489
]
Sean Owen commented on SPARK-20202:
-----------------------------------
Alrighty, you can leave the status for now, but generally committers set
Blocker. I'm not entirely clear this blocks a release, not yet.
You're absolutely right, but, the hive fork with binaries and source is part of
this project. At least, that's the idea. For example, this is notionally voted
on and released with each Spark release, but the binary/source of this fork
project isn't separately, explicitly, voted on and separately released. I think
that should occur for avoidance of doubt, that this is a blessed artifact of
the Spark project. Would this answer your process and policy concerns about the
release? It's not pretty but I think that's within the law.
Of course, it's no answer in the long term. The goal is to not have to use the
fork at all. If Hive packaging changes are already in place to make it
unnecessary, great (is that all there is to it, everyone?) I don't know if that
presents a solution for earlier versions of Hive. This fork thing may persist
in existing branches, but it has to at least be released and used in a proper
way. This may need fixes right now.
> Remove references to org.spark-project.hive
> -------------------------------------------
>
> Key: SPARK-20202
> URL: https://issues.apache.org/jira/browse/SPARK-20202
> Project: Spark
> Issue Type: Bug
> Components: Build, SQL
> Affects Versions: 1.6.4, 2.0.3, 2.1.1
> Reporter: Owen O'Malley
> Priority: Blocker
>
> Spark can't continue to depend on their fork of Hive and must move to
> standard Hive versions.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
