You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The nested case is somewhat confusing. At first glance, it's not clear what y refers to in this statement:
ALTERTABLE 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:
ALTERTABLE t ADD COLUMN c BIGINT AFTER a.b.y
The text was updated successfully, but these errors were encountered:
Follow-up of #20914. The PR supports position 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: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 roota
aftery
.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:The text was updated successfully, but these errors were encountered: