Skip to content

Spec: Clarify per-file name mapping fallback - #19037

Open
manuzhang wants to merge 1 commit into
apache:mainfrom
manuzhang:codex/spec-per-file-name-mapping
Open

manuzhang wants to merge 1 commit into
apache:mainfrom
manuzhang:codex/spec-per-file-name-mapping

Conversation

@manuzhang

@manuzhang manuzhang commented Nov 19, 2026 •

Copy link
Copy Markdown
Member

#10835 introduced wording that suggests readers can mix embedded field IDs and name mapping in the same file. This restores the original per-file rule and bases the decision on the full file schema so it is independent of projection. For a list or map with missing child IDs, the proposed behavior treats the whole container as absent and uses the existing missing-field rules. Dev-list discussion, verification fixture.

Validation passed with the site's Markdown linter, a render of the Column Projection section, ./gradlew spotlessApply, and git diff --check.


AI Disclosure

  • Model: GPT-6
  • Platform/Tool: Codex
  • Human Oversight: reviewed
  • Prompt Summary: Review the dev-list discussion and draft the Column Projection spec wording and follow-up PR.

@github-actions github-actions Bot added the Specification Issues that may introduce spec changes. label Nov 19, 2026
The column projection rules can be read as permitting name mapping for individual fields in an ID-bearing file. Clarify file-level resolution and how missing nested IDs are handled.

Generated-by: Codex
@manuzhang
manuzhang force-pushed the codex/spec-per-file-name-mapping branch from b3ef5fd to bb93bec Compare November 19, 2026 14:58

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Specification Issues that may introduce spec changes.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants