[jira] [Reopened] (FLINK-33028) FLIP-348: Make expanding behavior of virtual metadata columns configurable

2024-02-20 Thread Timo Walther (Jira)


 [ 
https://issues.apache.org/jira/browse/FLINK-33028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timo Walther reopened FLINK-33028:
--

> FLIP-348: Make expanding behavior of virtual metadata columns configurable
> --
>
> Key: FLINK-33028
> URL: https://issues.apache.org/jira/browse/FLINK-33028
> Project: Flink
>  Issue Type: New Feature
>  Components: Table SQL / API, Table SQL / Planner
>Reporter: Timo Walther
>Assignee: Timo Walther
>Priority: Major
> Fix For: 1.19.0
>
>
> Many SQL vendors expose additional metadata via so-called "pseudo columns" or 
> "system columns" next to the physical columns.
> However, those columns should not be selected by default when expanding 
> SELECT *.  Also for the sake of backward compatibility. Flink SQL already 
> offers pseudo columns next to the physical columns exposed as metadata 
> columns.
> This proposal suggests to evolve the existing column design slightly to be 
> more useful for platform providers.
> https://cwiki.apache.org/confluence/x/_o6zDw



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Reopened] (FLINK-33028) FLIP-348: Make expanding behavior of virtual metadata columns configurable

2023-09-29 Thread Timo Walther (Jira)


 [ 
https://issues.apache.org/jira/browse/FLINK-33028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timo Walther reopened FLINK-33028:
--

> FLIP-348: Make expanding behavior of virtual metadata columns configurable
> --
>
> Key: FLINK-33028
> URL: https://issues.apache.org/jira/browse/FLINK-33028
> Project: Flink
>  Issue Type: New Feature
>  Components: Table SQL / API, Table SQL / Planner
>Reporter: Timo Walther
>Assignee: Timo Walther
>Priority: Major
> Fix For: 1.19.0
>
>
> Many SQL vendors expose additional metadata via so-called "pseudo columns" or 
> "system columns" next to the physical columns.
> However, those columns should not be selected by default when expanding 
> SELECT *.  Also for the sake of backward compatibility. Flink SQL already 
> offers pseudo columns next to the physical columns exposed as metadata 
> columns.
> This proposal suggests to evolve the existing column design slightly to be 
> more useful for platform providers.
> https://cwiki.apache.org/confluence/x/_o6zDw



--
This message was sent by Atlassian Jira
(v8.20.10#820010)