(flink) flink-bundle-shade-hive1 profile fails to build in hudi-flink-bundle
- Dominant language
- Java
- Stars
- 6.2k
- Forks
- 2.5k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 111
Description
### Bug Description
**What happened:**
Building packaging/hudi-flink-bundle with the flink-bundle-shade-hive1 profile fails during Maven dependency collection. The profile pins hive.version=1.1.0, and Hive 1.1.0's transitive dependency graph (through Calcite) requires eigenbase:eigenbase-properties:1.1.4. That artifact is not available in Maven Central (it was historically published only to the now-defunct conjars.org repository), so the build aborts with a DependencyResolutionException before the shade plugin runs:
[ERROR] Failed to execute goal on project hudi-flink1.18-bundle: Could not collect dependencies
for project org.apache.hudi:hudi-flink1.18-bundle:jar:1.3.0-SNAPSHOT
[ERROR] Failed to read artifact descriptor for eigenbase:eigenbase-properties:jar:1.1.4
[ERROR] The following artifacts could not be resolved:
eigenbase:eigenbase-properties:pom:1.1.4 (absent)
**What you expected:**
The flink-bundle-shade-hive1 profile should either build successfully, or if Hive 1.x is no longer supported be removed (or its unresolvable legacy dependencies excluded / a working repository configured) so the profile list doesn't contain a permanently broken option.
**Steps to reproduce:**
git checkout master
mvn clean package -pl packaging/hudi-flink-bundle -am \
-Dflink1.18 -Pflink-bundle-shade-hive1 -DskipTests -Drat.skip=true
Observe the build fail with Could not resolve eigenbase:eigenbase-properties:1.1.4.
### Environment
**Hudi version:** master
**Query engine:** Flink
**Relevant configs:**
### Logs and Stack Trace
_No response_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start in packaging/hudi-flink-bundle by running the provided Maven command with the flink-bundle-shade-hive1 profile and tracing the hive.version=1.1.0 dependency collection failure. Check whether the profile is expected to remain supported and identify the project-approved resolution for the unavailable eigenbase artifact. Done means the profile builds successfully or the broken option is removed or otherwise made explicitly workable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100