[
https://issues.apache.org/jira/browse/HIVE-30010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18111238#comment-18111238
]
Rick Weber commented on HIVE-30010:
-----------------------------------
I provided a snippet of the build under the `Environment` field above. In
short, if you execute
{code:java}
mvn clean package -DskipTests -Pitests -Pdist -pl
\!:hive-accumulo-handler,\!:metastore-tools-common,\!:hive-metastore-benchmarks,\!:hive-druid-handler
{code}
The build will fail indicating:
{code:java}
[ERROR] Failed to execute goal on project hive-packaging: Could not resolve
dependencies for project org.apache.hive:hive-packaging:pom:4.2.1: The
following artifacts could not be resolved:
org.apache.hive:hive-druid-handler:jar:4.2.1,
org.apache.hive:hive-accumulo-handler:jar:4.2.1: Could not find artifact
org.apache.hive:hive-druid-handler:jar:4.2.1 in central
(https://repo.maven.apache.org/maven2) -> [Help 1]
{code}
Essentially this is due to the jars NOT being publicly published. My build
environment is firewalled off from the public internet, and we access the Maven
Repository through an Artifactory instance. `hive-druid-handler` itself cannot
be directly built since `org.hyperic:sigar:jar:1.6.5.132` is stored on a
separate Maven repository that is not currently being mirrored internally.
I believe the way you're building it causes the built Jira's to be added to
your local Maven cache directory (.m2) rather than being retrieve externally.
Mainly though, the crux of the Jira is that all of the Artifacts from the
v4.2.1 build were not published as had been in the past.
Thanks
> All Hive Jar's were not published to public Maven repositories
> --------------------------------------------------------------
>
> Key: HIVE-30010
> URL: https://issues.apache.org/jira/browse/HIVE-30010
> Project: Hive
> Issue Type: Bug
> Components: Accumulo Storage Handler, distribution, Druid integration
> Affects Versions: 4.2.1
> Environment: Local Dev environment. Maven executed with flags
> similar to:
> {code:java}
> mvn <LOCAL_OPTS> -Pdist -Piceberg -pl
> !:hive-accumulo-handler,!:metastore-tools-common,!:hive-metastore-benchmarks,!:hive-druid-handler
> {code}
> Reporter: Rick Weber
> Priority: Minor
>
> While attempting to build and bundle Apache Hive v4.2.1, the Packaging step
> fails to complete if the user does not request that `hive-druid-handler`
> and/or `hive-accumulor-handler` are excluded from the build.
> This build step succeeded in earlier versions, due to those Jar's being
> automatically downloaded to satisfy the dependencies. In the case of Hive
> v4.2.1, it appears that the Jars for both hive-accumulo-handler as well as
> hive-druid-handler *WERE NOT* published to the public repositories.
> Based on a brief e-mail exchange with [~zabetak] , it was verified via:
> {quote}Indeed there is a publishing problem of the jars in Maven. The druid
> and accumulo jars for 4.2.1 are not present in central [1] nor in the Apache
> maven repository [2]. I guess some step in the preparation of the release
> candidate was performed differently (possibly a profile skipping those
> modules) and we failed to catch it during the vote. Please log a JIRA ticket
> for tracking this further and we will see how we can rectify this.{quote}
>
> NOTE: The Druid handler has been removed from v4.3.0 onward, however this
> affects local builds that do _NOT_ build the above Jar's
>
> Links to both missing jars (for verification): *
> [https://mvnrepository.com/artifact/org.apache.hive/hive-druid-handler]
> * [https://mvnrepository.com/artifact/org.apache.hive/hive-accumulo-handler]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
