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

Support FIRST, AFTER and LAST options for nested fields #24513

Open
ebyhr opened this issue Dec 18, 2024 · 0 comments
Open

Support FIRST, AFTER and LAST options for nested fields #24513

ebyhr opened this issue Dec 18, 2024 · 0 comments

Comments

@ebyhr
Copy link
Member

ebyhr commented Dec 18, 2024

Follow-up of #20914. This PR supports those options only for top level columns.

Quote from #20914 (review):

The nested case is somewhat confusing. At first glance, it's not clear what y refers to in this statement:

ALTER TABLE t ADD COLUMN a.b.c BIGINT AFTER y

It's meant to be a field within a.b, but that's not immediately obvious. It could, as well, be a top-level column and the statement could be a short hand for creating all the required nested fields with the root a after y.

The following structure would be more natural, but it only works with AFTER and it's incompatible with how nested columns are handled in general:

ALTER TABLE t ADD COLUMN c BIGINT AFTER a.b.y
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant