[ 
https://issues.apache.org/jira/browse/HIVE-30010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18115335#comment-18115335
 ] 

Sai Hemanth Gantasala commented on HIVE-30010:
----------------------------------------------

[~tsetem] - The missing jars are now published in the central repository. I'll 
now close the Jira as resolved. I would like to outline the following the steps

*What went wrong:* The 4.2.1 Maven deploy was incomplete(due to network 
issues): core JARs (e.g. {{{}hive-exec{}}}) reached Maven Central, but many 
modules that were published for 4.2.0 were not, including 
{{{}hive-accumulo-handler{}}}, {{{}hive-druid-handler{}}}, and other 
handlers/Iceberg artifacts. Builds that exclude those modules and pull them 
from Maven (as in HIVE-30010) failed; full source builds still worked. We 
didn’t catch this in the RC vote because we didn’t verify all published modules 
against the previous release.

*What was done to Fix:*
 # Compared 4.2.0 vs 4.2.1 on Maven Central and listed 23 missing modules.
 # From {{rel/release-4.2.1}}: {{mvn install}} with {{-pl <missing list> -am 
-DskipTests}} and {{-PerrorProne}} (required for {{{}iceberg/*{}}}).
 # {{mvn deploy}} with the same {{-pl}} only (no {{{}-am{}}}), 
{{{}-Papache-release{}}}, release settings + GPG; then close/release staging in 
Nexus.
 # Confirmed all 23 JARs on Maven Central.

*If it happens again:* After deploy, spot-check handlers/Iceberg (and compare 
to prior GA). Partial republish: tag → install with {{-pl -am}} (+ 
{{-PerrorProne}} for Iceberg) → deploy {{-pl}} only → Nexus release.


I'll work updating the release page to run a script to avoid the same issue in 
the future.

> 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
>            Assignee: Sai Hemanth Gantasala
>            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)

Reply via email to