[jira] [Updated] (FLINK-20368) Supports custom operator name for Flink SQL
[ https://issues.apache.org/jira/browse/FLINK-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-20368: --- Labels: auto-deprioritized-major auto-deprioritized-minor (was: auto-deprioritized-major stale-minor) Priority: Not a Priority (was: Minor) This issue was labeled "stale-minor" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Minor, please raise the priority and ask a committer to assign you the issue or revive the public discussion. > Supports custom operator name for Flink SQL > --- > > Key: FLINK-20368 > URL: https://issues.apache.org/jira/browse/FLINK-20368 > Project: Flink > Issue Type: Improvement > Components: Table SQL / API >Affects Versions: 1.12.0 >Reporter: Danny Chen >Priority: Not a Priority > Labels: auto-deprioritized-major, auto-deprioritized-minor > > A request from USER mailing list from Kevin Kwon: > For SQLs, I know that the operator ID assignment is not possible now since > the query optimizer may not be backward compatible in each release > But are DDLs also affected by this? > for example, > CREATE TABLE mytable ( > id BIGINT, > data STRING > ) with ( > connector = 'kafka' > ... > id = 'mytable' > name = 'mytable' > ) > and we can save all related checkpoint data -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (FLINK-20368) Supports custom operator name for Flink SQL
[ https://issues.apache.org/jira/browse/FLINK-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-20368: --- Labels: auto-deprioritized-major stale-minor (was: auto-deprioritized-major) 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. > Supports custom operator name for Flink SQL > --- > > Key: FLINK-20368 > URL: https://issues.apache.org/jira/browse/FLINK-20368 > Project: Flink > Issue Type: Improvement > Components: Table SQL / API >Affects Versions: 1.12.0 >Reporter: Danny Chen >Priority: Minor > Labels: auto-deprioritized-major, stale-minor > > A request from USER mailing list from Kevin Kwon: > For SQLs, I know that the operator ID assignment is not possible now since > the query optimizer may not be backward compatible in each release > But are DDLs also affected by this? > for example, > CREATE TABLE mytable ( > id BIGINT, > data STRING > ) with ( > connector = 'kafka' > ... > id = 'mytable' > name = 'mytable' > ) > and we can save all related checkpoint data -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-20368) Supports custom operator name for Flink SQL
[ https://issues.apache.org/jira/browse/FLINK-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-20368: --- Priority: Minor (was: Major) > Supports custom operator name for Flink SQL > --- > > Key: FLINK-20368 > URL: https://issues.apache.org/jira/browse/FLINK-20368 > Project: Flink > Issue Type: Improvement > Components: Table SQL / API >Affects Versions: 1.12.0 >Reporter: Danny Chen >Priority: Minor > Labels: auto-deprioritized-major > > A request from USER mailing list from Kevin Kwon: > For SQLs, I know that the operator ID assignment is not possible now since > the query optimizer may not be backward compatible in each release > But are DDLs also affected by this? > for example, > CREATE TABLE mytable ( > id BIGINT, > data STRING > ) with ( > connector = 'kafka' > ... > id = 'mytable' > name = 'mytable' > ) > and we can save all related checkpoint data -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-20368) Supports custom operator name for Flink SQL
[ https://issues.apache.org/jira/browse/FLINK-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-20368: --- Labels: auto-deprioritized-major (was: stale-major) > Supports custom operator name for Flink SQL > --- > > Key: FLINK-20368 > URL: https://issues.apache.org/jira/browse/FLINK-20368 > Project: Flink > Issue Type: Improvement > Components: Table SQL / API >Affects Versions: 1.12.0 >Reporter: Danny Chen >Priority: Major > Labels: auto-deprioritized-major > > A request from USER mailing list from Kevin Kwon: > For SQLs, I know that the operator ID assignment is not possible now since > the query optimizer may not be backward compatible in each release > But are DDLs also affected by this? > for example, > CREATE TABLE mytable ( > id BIGINT, > data STRING > ) with ( > connector = 'kafka' > ... > id = 'mytable' > name = 'mytable' > ) > and we can save all related checkpoint data -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-20368) Supports custom operator name for Flink SQL
[ https://issues.apache.org/jira/browse/FLINK-20368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-20368: --- Labels: stale-major (was: ) > Supports custom operator name for Flink SQL > --- > > Key: FLINK-20368 > URL: https://issues.apache.org/jira/browse/FLINK-20368 > Project: Flink > Issue Type: Improvement > Components: Table SQL / API >Affects Versions: 1.12.0 >Reporter: Danny Chen >Priority: Major > Labels: stale-major > > A request from USER mailing list from Kevin Kwon: > For SQLs, I know that the operator ID assignment is not possible now since > the query optimizer may not be backward compatible in each release > But are DDLs also affected by this? > for example, > CREATE TABLE mytable ( > id BIGINT, > data STRING > ) with ( > connector = 'kafka' > ... > id = 'mytable' > name = 'mytable' > ) > and we can save all related checkpoint data -- This message was sent by Atlassian Jira (v8.3.4#803005)
