[
https://issues.apache.org/jira/browse/FLINK-28220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
JustinLee updated FLINK-28220:
------------------------------
Description:
when users want to Create Table A Like B , they can choose to include or
exclude options, computed columns ,etc. But it's mandatory that table A should
inherit all physical columns of table B, which may cause inconvenience in some
scenes , such as table A has its own schema and just want to inherit the
options of table B.
In our production case, sometimes we need to consume kafka table as RAW format
which has an original JSON format , so we wound Create Table A (data string )
with ('format'='raw') Like B, but it encounters an error saying table A has
more than one physical columns because of inheriting these columns from table
B.
so I think it would be more flexible to provide the option to include or
exclude physical columns when Using Create Table .. Like ..
was:
when users want to Create Table A Like B , they can choose to include or
exclude options, computed columns ,etc. But it's mandatory that table A should
inherit all physical columns of table B, which may cause inconvenience in some
scenes , such as table A has its own schema and just want to inherit the
options of table B.
so I think it would be more flexible to provide the option to include or
exclude physical columns when Using Create Table .. Like ..
> Create Table Like support excluding physical columns
> ----------------------------------------------------
>
> Key: FLINK-28220
> URL: https://issues.apache.org/jira/browse/FLINK-28220
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / API
> Affects Versions: 1.15.0
> Reporter: JustinLee
> Priority: Major
>
> when users want to Create Table A Like B , they can choose to include or
> exclude options, computed columns ,etc. But it's mandatory that table A
> should inherit all physical columns of table B, which may cause inconvenience
> in some scenes , such as table A has its own schema and just want to inherit
> the options of table B.
> In our production case, sometimes we need to consume kafka table as RAW
> format which has an original JSON format , so we wound Create Table A (data
> string ) with ('format'='raw') Like B, but it encounters an error saying
> table A has more than one physical columns because of inheriting these
> columns from table B.
> so I think it would be more flexible to provide the option to include or
> exclude physical columns when Using Create Table .. Like ..
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
