deniskuzZ opened a new pull request, #6876: URL: https://github.com/apache/hive/pull/6876
### What changes were proposed in this pull request? - `packaging/pom.xml` depends on the thin `hive-beeline` jar again, next to `hive-beeline:standalone` - `bin.xml` excludes `org.apache.hive:hive-beeline:*:standalone` from `lib`, as it already does for `hive-jdbc:*:standalone` - `beeline.xml` includes only `org.apache.hive:hive-beeline:jar:standalone`, so the beeline tarball keeps what HIVE-29869 gave it ### Why are the changes needed? HIVE-29869 replaced the beeline tarball's `jar-with-dependencies.jar` with a dependency of packaging on `hive-beeline:standalone`. `bin.xml`'s `lib` takes every packaging dependency except its excludes, so the main distribution's `lib` has carried the standalone jar since, instead of the thin one. It holds 89,592 unrelocated classes (hive-common incl. `HiveConf`, Hadoop, Guava, Curator, Jetty, Derby, gRPC/Netty, ...), and everything in `lib` is on the classpath of HiveServer2, the metastore, LLAP and the Tez AM: each of those classes is loaded from whichever jar the `lib/*` wildcard lists first. With a `hive-common` newer than the standalone, HiveServer2 loaded the standalone's `HiveConf` and every query failed with `NoSuchFieldError: HiveConf$ConfVars ...`. ### Does this PR introduce _any_ user-facing change? The distribution's `lib` has `hive-beeline-<version>.jar` instead of `hive-beeline-<version>-standalone.jar`; `bin/beeline` uses it as before HIVE-29869. The beeline tarball is unchanged. ### How was this patch tested? To do: `mvn package -Pdist -DskipTests`, then check that the main tarball's `lib` has the thin `hive-beeline` jar (with `super-csv`, `jline`) and no `-standalone`, that the beeline tarball's listing is unchanged against master, and run `bin/beeline` against HiveServer2. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
