Doris-Breakwater commented on issue #70000: URL: https://github.com/apache/doris/issues/70000#issuecomment-6580061855
Breakwater-GitHub-Analysis-Slot: slot_a557bf4827bb The missing dependency is independently reproducible. This is an FE build/dependency-publication issue: the checked source revisions request a snapshot that the configured Apache repository no longer serves. A replacement snapshot is a plausible immediate unblock, but its availability alone does not establish runtime compatibility. **Verified evidence (2026-11-02 UTC)** - The issue is open with no labels at the time of inspection. Suggested triage ownership: FE/build and the maintainers of the Doris JE artifact; prioritize clean-build restoration. - The local upstream revisions and public POMs agree on `18.3.14-doris-SNAPSHOT`: [master](https://github.com/apache/doris/blob/8e10b235cf030d486b6840cfd64b6218ab515e6d/fe/pom.xml#L300), [branch-4.1](https://github.com/apache/doris/blob/b4afc8c693ef6fbb2a657f0a5fcbcd14e52a30d2/fe/pom.xml#L281), [branch-4.0](https://github.com/apache/doris/blob/8a9961723ea4be00cdf923c60759607202c7e2e7/fe/pom.xml#L271), and [4.1.5-release](https://github.com/apache/doris/blob/917b20be83878e98f94e3ebf7efccc80346e3e50/fe/pom.xml#L285). - In 4.1.5, `fe-core` [declares `org.apache.doris:je`](https://github.com/apache/doris/blob/917b20be83878e98f94e3ebf7efccc80346e3e50/fe/fe-core/pom.xml#L238); the parent POM manages its version and [configures the Apache snapshot repository](https://github.com/apache/doris/blob/917b20be83878e98f94e3ebf7efccc80346e3e50/fe/pom.xml#L2123). Resolution therefore fails before FE compilation. Maven resolves a snapshot through metadata for that particular base version; publishing `18.3.17` does not satisfy a dependency on `18.3.14`. See [Maven's snapshot-resolution explanation](https://maven.apache.org/repositories/remote.html). - The [18.3.14 metadata URL](https://repository.apache.org/content/repositories/snapshots/org/apache/doris/je/18.3.14-doris-SNAPSHOT/maven-metadata.xml) returns HTTP 404. The [18.3.17 metadata](https://repository.apache.org/content/repositories/snapshots/org/apache/doris/je/18.3.17-doris-SNAPSHOT/maven-metadata.xml) returns HTTP 200 and identifies `18.3.17-doris-20261102.063631-1`; its POM and JAR are available. - With Maven 3.9.14, JDK 17.0.16, empty user/global settings, and an initially empty isolated local repository, `maven-dependency-plugin:3.8.1:get` fails for `18.3.14` and succeeds for `18.3.17`. Both checks used the Apache snapshot URL and `-Dtransitive=false`, isolating this artifact. This is **not** a full FE build or transitive-dependency validation. The reported 477 catalog tests have not been independently rerun. **What remains unproven** The current [repository version metadata](https://repository.apache.org/content/repositories/snapshots/org/apache/doris/je/maven-metadata.xml) lists **both `18.3.17` and `18.3.18`**. Thus the assertion that this repository retains only one snapshot base version is not supported by its present contents. Removal/cleanup of `18.3.14` is consistent with the observations, but the deletion time, actor, and retention policy require repository-administration evidence. Cached copies can explain differing build outcomes; they do not establish why the remote artifact disappeared. **Recommended next steps** 1. Have the artifact maintainers confirm the intended replacement and its source revision. `18.3.17` resolves and is a reasonable candidate for an unblock PR, subject to compatibility validation; also evaluate the published `18.3.18`. The public [18.3.18 change](https://github.com/apache/doris-thirdparty/commit/70324a2452e4ff717c872e431b5b385c82a54f84) includes SSL certificate-monitor lifecycle changes, so these versions should not be treated as interchangeable uploads. 2. Validate the chosen version on each affected maintained branch using a fresh Maven repository and the normal FE build. Include `BDBEnvironmentTest`, `BDBJEJournalTest`, and `BDBJournalCursorTest`, plus restart/replay and mixed-version replication checks for supported upgrade paths. This scope follows the code: [BDBJEJournal.write](https://github.com/apache/doris/blob/917b20be83878e98f94e3ebf7efccc80346e3e50/fe/fe-core/src/main/java/org/apache/doris/journal/bdbje/BDBJEJournal.java#L130) commits journal transactions through JE, while [BDBEnvironment](https://github.com/apache/doris/blob/917b20be83878e98f94e3ebf7efccc80346e3e50/fe/fe-core/src/main/java/org/apache/doris/journal/bdbje/BDBEnvironment.java#L171) configures durability and opens the replicated environment. The catalog-only test selection does not directly select those journal tests. 3. For a durable fix, publish and consume a maintained, immutable non-snapshot Doris JE release through the project's release process, and add a periodic clean-cache dependency-resolution check. A branch POM bump alone does not restore reproducibility of existing release tags; decide separately how to preserve or restore their exact historical artifacts. Repeated `-U` retries cannot retrieve an artifact that remains absent upstream. For the PR, please attach the exact Doris checkout SHA, Maven/JDK versions, build/test commands and reports, and the resolved JE timestamp/checksum. These are needed to assess the replacement, not to establish the already-reproduced missing-artifact failure. Repository cleanup/retention records are needed only to confirm the removal mechanism. No runtime query profile is needed for this build-resolution issue. -- 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]
