REST Spec: add labels field to LoadTableResult#15750
Draft
laskoviymishka wants to merge 1 commit intoapache:mainfrom
Draft
REST Spec: add labels field to LoadTableResult#15750laskoviymishka wants to merge 1 commit intoapache:mainfrom
laskoviymishka wants to merge 1 commit intoapache:mainfrom
Conversation
Add optional labels field to LoadTableResult for catalog-specific metadata enrichment. Labels are ephemeral API-level annotations — not table state. They do not modify table metadata files or create commits. Catalogs MAY populate labels to provide operational context (ownership, classification, cost attribution, semantic hints). Engines MAY use labels or ignore them entirely. Labels are backward compatible — older clients ignore unknown fields. New schemas: Labels, ColumnLabels (column labels keyed by field-id for stability across schema evolution).
laskoviymishka
force-pushed
the
labels-in-load-table-response
branch
from
acdb80a to
a80fc1a
Compare
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
1 participant
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.
Add optional labels field to LoadTableResult for catalog-specific metadata enrichment. Labels are ephemeral API-level annotations — not table state. They do not modify table metadata files or create commits.
Catalogs MAY populate labels to provide operational context (ownership, classification, cost attribution, semantic hints). Engines MAY use labels or ignore them entirely. Labels are backward compatible — older clients ignore unknown fields.
New schemas: Labels, ColumnLabels (column labels keyed by field-id for stability across schema evolution).
Proof-of-concept for the IRC Labels proposal: #15521.