Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Logical schema exposed to engine should not include column mapping metadata #583

Open
scovich opened this issue Dec 10, 2024 · 0 comments
Open
Labels
bug Something isn't working

Comments

@scovich
Copy link
Collaborator

scovich commented Dec 10, 2024

Describe the bug

Column mapping field metadata is an internal Delta detail and unsuspecting engines should not be exposed to it as the metadata could propagate in unwanted ways (such as from source to target as part of a CTAS).

To Reproduce

Create a column mapped table. Snapshot::schema includes column mapping metadata.

Expected behavior

It should not.

Additional context

No response

@scovich scovich added the bug Something isn't working label Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant