Skip to content

[gs] Map gs.* config entries to fs.gs.* Hadoop config keys - #8936

Open
thswlsqls wants to merge 1 commit into
apache:masterfrom
thswlsqls:fix/gs-map-config-prefix
Open

[gs] Map gs.* config entries to fs.gs.* Hadoop config keys#8936
thswlsqls wants to merge 1 commit into
apache:masterfrom
thswlsqls:fix/gs-map-config-prefix

Conversation

@thswlsqls

Copy link
Copy Markdown
Contributor

Purpose

fix #8934

  • GSFileIO.configure() accepts gs. and fs.gs. prefixes but passes keys to the Hadoop config unchanged, so gs.* options are silently ignored by the gcs-connector, which only reads fs.gs.* keys.
  • Translate accepted prefixes to fs.gs.*, matching sibling S3FileIO (s3.* -> fs.s3a.*) and AzureFileIO (azure.* -> fs.azure.*), and the upstream Flink flink-gs-fs-hadoop ConfigUtils this list was ported from.
  • Align the log with the S3/Azure canonical form: LOG.debug with key names only, no values (precedent: [cosn] Log Hadoop config entries at debug level instead of warn #8554).

Tests

  • Added GSFileIOTest covering gs.* key mapping, fs.gs.* key preservation, and unrelated keys being ignored.
  • mvn -pl paimon-filesystems/paimon-gs-impl clean install — 3 tests passed (unit test only; no GCS backend available locally).

GSFileIO accepted both gs. and fs.gs. prefixed options but copied
matching keys into the Hadoop configuration unchanged, so gs.* entries
were silently ignored by the gcs-connector, which only reads fs.gs.*
keys. Translate the accepted prefixes to fs.gs.* like S3FileIO and
AzureFileIO do for their prefixes, and log the mapping at debug level
without values.

Generated-by: Claude Code
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] gs.* catalog options are silently ignored by GSFileIO

1 participant