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
Since #20203 (which resolves #12199), users are free to call [ADD | DROP] COLUMN for a table no matter whether its schema is derived from external system (i.e., schema registry).
However, the behavior is inconsistent when it comes to ALTER SOURCE, since they are on different code paths.
ALTER SOURCE DROP COLUMN is generally unsupported.
Only ALTER SOURCE REFRESH SCHEMA is supported for schema change on a source with schema registry.
Since #20203 (which resolves #12199), users are free to call
[ADD | DROP] COLUMN
for a table no matter whether its schema is derived from external system (i.e., schema registry).However, the behavior is inconsistent when it comes to
ALTER SOURCE
, since they are on different code paths.ALTER SOURCE DROP COLUMN
is generally unsupported.ALTER SOURCE REFRESH SCHEMA
is supported for schema change on a source with schema registry.ALTER SOURCE FORMAT .. ENCODE .. (...)
(introduced in feat: implementALTER SOURCE xx FORMAT xx ENCODE xx (...)
#14057)The text was updated successfully, but these errors were encountered: