[
https://issues.apache.org/jira/browse/FLINK-10448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-10448:
-----------------------------------
Labels: auto-deprioritized-major auto-unassigned stale-minor (was:
auto-deprioritized-major auto-unassigned)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> VALUES clause is translated into a separate operator per value
> --------------------------------------------------------------
>
> Key: FLINK-10448
> URL: https://issues.apache.org/jira/browse/FLINK-10448
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / API
> Affects Versions: 1.6.1
> Reporter: Timo Walther
> Priority: Minor
> Labels: auto-deprioritized-major, auto-unassigned, stale-minor
>
> It seems that a SQL VALUES clause uses one operator per value under certain
> conditions which leads to a complicated job graph. Given that we need to
> compile code for every operator in the open method and have other overhead as
> well, this looks inefficient to me.
> For example, the following query creates and unions 6 operators together:
> {code}
> SELECT *
> FROM (
> VALUES
> (1, 'Bob', CAST(0 AS BIGINT)),
> (22, 'Alice', CAST(0 AS BIGINT)),
> (42, 'Greg', CAST(0 AS BIGINT)),
> (42, 'Greg', CAST(0 AS BIGINT)),
> (42, 'Greg', CAST(0 AS BIGINT)),
> (1, 'Bob', CAST(0 AS BIGINT)))
> AS UserCountTable(user_id, user_name, user_count)
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
