HADOOP-19851. Point S3A GCS docs to the hadoop-gcp connector - #8639
Open
johntomcat7408-cmyk wants to merge 1 commit into
Open
HADOOP-19851. Point S3A GCS docs to the hadoop-gcp connector#8639johntomcat7408-cmyk wants to merge 1 commit into
johntomcat7408-cmyk wants to merge 1 commit into
Conversation
Generated-by: Codex
Contributor
|
ℹ️ Cloud-AWS manual trigger instructions: S3A tests must be manually triggered for fork pull requests. A maintainer should:
fork head: |
|
🎊 +1 overall
This message was automatically generated. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of PR
This PR updates the S3A third-party-store documentation for Google Cloud
Storage to point users to Hadoop's
hadoop-gcpgs:connector configurationpage instead of the external Dataproc connector page.
The existing S3A compatibility scenarios, configuration, limitations, and test
guidance remain unchanged. This is a documentation-only change: it does not
modify Java code, dependencies, public APIs, configuration defaults or
examples, endpoints, regions, or runtime behavior.
Jira: https://issues.apache.org/jira/browse/HADOOP-19851
HADOOP-19851 supplied the problem statement and requested direction. PR #8058
was reviewed only because it also changes this Markdown file; no unmerged code,
commit, or wording from that PR was reused. This patch was authored
independently against the current
trunkbaseline.Contains content generated by Codex
How was this patch tested?
Environment: Windows x86_64, Eclipse Temurin 17.0.19, and the project Maven
Wrapper with Maven 3.9.15.
Installed the reactor artifacts required by the two affected site modules:
All 36 reactor projects completed successfully. This command skipped tests
and was used only to prepare local site artifacts.
Ran the targeted site build twice, as required by
BUILDING.txt:Both runs completed with
BUILD SUCCESS. The generatedthird_party_stores.htmlcontained../../../hadoop-gcp/tools/hadoop-gcp/Configuration.html; resolving thathref from the generated source page matched the generated
Configuration.htmlfile, which existed. The newgs:guidance was presentand the old Dataproc connector link was absent.
Ran Apache Yetus 0.14.1 from an isolated baseline worktree:
Yetus reported
+1 overall. The Hadoop personality classified the pureMarkdown patch as
nobuild, so this did not run Java compilation or tests.git diff --check upstream/trunk...HEADcompleted without errors.The root-reactor aggregate site was not completed because the local environment
did not contain every artifact required by the full reactor; one Maven Central
request was also reset. The two affected modules' generated pages and their
cross-module href were verified directly. Java tests and object-store
integration tests are not applicable because the final diff changes no code,
configuration, endpoint, region, or runtime semantics.
For code changes:
N/A: this patch changes documentation guidance only and does not change an object-store endpoint or runtime behavior.
N/A: no dependencies are added.
LICENSE,LICENSE-binary,NOTICE-binaryfiles?N/A: the change adds no dependency or third-party material requiring a license or notice update.
AI Tooling
If an AI tool was used:
where is the name of the AI tool used.
https://www.apache.org/legal/generative-tooling.html