[jira] [Updated] (FLINK-15859) Unify identifiers in the interface methods of CatalogManager

2024-03-11 Thread lincoln lee (Jira) 


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

lincoln lee updated FLINK-15859:

Fix Version/s: (was: 1.19.0)

> Unify identifiers in the interface methods of CatalogManager
> 
>
> Key: FLINK-15859
> URL: https://issues.apache.org/jira/browse/FLINK-15859
> Project: Flink
>  Issue Type: Improvement
>  Components: Table SQL / API
>Reporter: Dawid Wysakowicz
>Priority: Minor
>  Labels: auto-deprioritized-major
> Fix For: 1.20.0
>
>
> We're not being too consistent with the type of identifier that the 
> FunctionCatalog/CatalogManager accepts.
> Some methods accept {{UnresolvedIdentifier}} e.g. 
> {{FunctionCatalog#registerTemporaryCatalogFunction}}, 
> {{CatalogManager#dropTemporaryView}}. 
> Some resolved {{ObjectIdentifier}} e.g. 
> {{CatalogManager#createTemporaryTable}}, {{CatalogManager#createTable}}.
> I am not sure which one should we prefer. If we go with the 
> {{UnresolvedIdentifier}} the benefit is that we always qualify it in a 
> {{Catalog*}}. The downside is that we would use {{UnresolvedIdentifier}} in 
> {{*Operations}}, (e.g. {{CreateTableOperation}} etc.), whereas we said that 
> all Operations should be fully resolved...



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

[jira] [Updated] (FLINK-15859) Unify identifiers in the interface methods of CatalogManager

2024-03-11 Thread lincoln lee (Jira) 


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

lincoln lee updated FLINK-15859:

Fix Version/s: 1.20.0

> Unify identifiers in the interface methods of CatalogManager
> 
>
> Key: FLINK-15859
> URL: https://issues.apache.org/jira/browse/FLINK-15859
> Project: Flink
>  Issue Type: Improvement
>  Components: Table SQL / API
>Reporter: Dawid Wysakowicz
>Priority: Minor
>  Labels: auto-deprioritized-major
> Fix For: 1.19.0, 1.20.0
>
>
> We're not being too consistent with the type of identifier that the 
> FunctionCatalog/CatalogManager accepts.
> Some methods accept {{UnresolvedIdentifier}} e.g. 
> {{FunctionCatalog#registerTemporaryCatalogFunction}}, 
> {{CatalogManager#dropTemporaryView}}. 
> Some resolved {{ObjectIdentifier}} e.g. 
> {{CatalogManager#createTemporaryTable}}, {{CatalogManager#createTable}}.
> I am not sure which one should we prefer. If we go with the 
> {{UnresolvedIdentifier}} the benefit is that we always qualify it in a 
> {{Catalog*}}. The downside is that we would use {{UnresolvedIdentifier}} in 
> {{*Operations}}, (e.g. {{CreateTableOperation}} etc.), whereas we said that 
> all Operations should be fully resolved...



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

[jira] [Updated] (FLINK-15859) Unify identifiers in the interface methods of CatalogManager

2023-10-13 Thread Jing Ge (Jira) 


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

Jing Ge updated FLINK-15859:

Fix Version/s: 1.19.0
   (was: 1.18.0)

> Unify identifiers in the interface methods of CatalogManager
> 
>
> Key: FLINK-15859
> URL: https://issues.apache.org/jira/browse/FLINK-15859
> Project: Flink
>  Issue Type: Improvement
>  Components: Table SQL / API
>Reporter: Dawid Wysakowicz
>Priority: Minor
>  Labels: auto-deprioritized-major
> Fix For: 1.19.0
>
>
> We're not being too consistent with the type of identifier that the 
> FunctionCatalog/CatalogManager accepts.
> Some methods accept {{UnresolvedIdentifier}} e.g. 
> {{FunctionCatalog#registerTemporaryCatalogFunction}}, 
> {{CatalogManager#dropTemporaryView}}. 
> Some resolved {{ObjectIdentifier}} e.g. 
> {{CatalogManager#createTemporaryTable}}, {{CatalogManager#createTable}}.
> I am not sure which one should we prefer. If we go with the 
> {{UnresolvedIdentifier}} the benefit is that we always qualify it in a 
> {{Catalog*}}. The downside is that we would use {{UnresolvedIdentifier}} in 
> {{*Operations}}, (e.g. {{CreateTableOperation}} etc.), whereas we said that 
> all Operations should be fully resolved...



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

[jira] [Updated] (FLINK-15859) Unify identifiers in the interface methods of CatalogManager

2023-03-23 Thread Xintong Song (Jira) 


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

Xintong Song updated FLINK-15859:
-
Fix Version/s: 1.18.0
   (was: 1.17.0)

> Unify identifiers in the interface methods of CatalogManager
> 
>
> Key: FLINK-15859
> URL: https://issues.apache.org/jira/browse/FLINK-15859
> Project: Flink
>  Issue Type: Improvement
>  Components: Table SQL / API
>Reporter: Dawid Wysakowicz
>Priority: Minor
>  Labels: auto-deprioritized-major
> Fix For: 1.18.0
>
>
> We're not being too consistent with the type of identifier that the 
> FunctionCatalog/CatalogManager accepts.
> Some methods accept {{UnresolvedIdentifier}} e.g. 
> {{FunctionCatalog#registerTemporaryCatalogFunction}}, 
> {{CatalogManager#dropTemporaryView}}. 
> Some resolved {{ObjectIdentifier}} e.g. 
> {{CatalogManager#createTemporaryTable}}, {{CatalogManager#createTable}}.
> I am not sure which one should we prefer. If we go with the 
> {{UnresolvedIdentifier}} the benefit is that we always qualify it in a 
> {{Catalog*}}. The downside is that we would use {{UnresolvedIdentifier}} in 
> {{*Operations}}, (e.g. {{CreateTableOperation}} etc.), whereas we said that 
> all Operations should be fully resolved...



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

[jira] [Updated] (FLINK-15859) Unify identifiers in the interface methods of CatalogManager

2022-08-22 Thread Godfrey He (Jira) 


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

Godfrey He updated FLINK-15859:
---
Fix Version/s: 1.17.0
   (was: 1.16.0)

> Unify identifiers in the interface methods of CatalogManager
> 
>
> Key: FLINK-15859
> URL: https://issues.apache.org/jira/browse/FLINK-15859
> Project: Flink
>  Issue Type: Improvement
>  Components: Table SQL / API
>Reporter: Dawid Wysakowicz
>Priority: Minor
>  Labels: auto-deprioritized-major
> Fix For: 1.17.0
>
>
> We're not being too consistent with the type of identifier that the 
> FunctionCatalog/CatalogManager accepts.
> Some methods accept {{UnresolvedIdentifier}} e.g. 
> {{FunctionCatalog#registerTemporaryCatalogFunction}}, 
> {{CatalogManager#dropTemporaryView}}. 
> Some resolved {{ObjectIdentifier}} e.g. 
> {{CatalogManager#createTemporaryTable}}, {{CatalogManager#createTable}}.
> I am not sure which one should we prefer. If we go with the 
> {{UnresolvedIdentifier}} the benefit is that we always qualify it in a 
> {{Catalog*}}. The downside is that we would use {{UnresolvedIdentifier}} in 
> {{*Operations}}, (e.g. {{CreateTableOperation}} etc.), whereas we said that 
> all Operations should be fully resolved...



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

[jira] [Updated] (FLINK-15859) Unify identifiers in the interface methods of CatalogManager

2022-04-13 Thread Yun Gao (Jira) 


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

Yun Gao updated FLINK-15859:

Fix Version/s: 1.16.0

> Unify identifiers in the interface methods of CatalogManager
> 
>
> Key: FLINK-15859
> URL: https://issues.apache.org/jira/browse/FLINK-15859
> Project: Flink
>  Issue Type: Improvement
>  Components: Table SQL / API
>Reporter: Dawid Wysakowicz
>Priority: Minor
>  Labels: auto-deprioritized-major
> Fix For: 1.15.0, 1.16.0
>
>
> We're not being too consistent with the type of identifier that the 
> FunctionCatalog/CatalogManager accepts.
> Some methods accept {{UnresolvedIdentifier}} e.g. 
> {{FunctionCatalog#registerTemporaryCatalogFunction}}, 
> {{CatalogManager#dropTemporaryView}}. 
> Some resolved {{ObjectIdentifier}} e.g. 
> {{CatalogManager#createTemporaryTable}}, {{CatalogManager#createTable}}.
> I am not sure which one should we prefer. If we go with the 
> {{UnresolvedIdentifier}} the benefit is that we always qualify it in a 
> {{Catalog*}}. The downside is that we would use {{UnresolvedIdentifier}} in 
> {{*Operations}}, (e.g. {{CreateTableOperation}} etc.), whereas we said that 
> all Operations should be fully resolved...



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (FLINK-15859) Unify identifiers in the interface methods of CatalogManager

2021-09-28 Thread Xintong Song (Jira) 


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

Xintong Song updated FLINK-15859:
-
Fix Version/s: (was: 1.14.0)
   1.15.0

> Unify identifiers in the interface methods of CatalogManager
> 
>
> Key: FLINK-15859
> URL: https://issues.apache.org/jira/browse/FLINK-15859
> Project: Flink
>  Issue Type: Improvement
>  Components: Table SQL / API
>Reporter: Dawid Wysakowicz
>Priority: Minor
>  Labels: auto-deprioritized-major
> Fix For: 1.15.0
>
>
> We're not being too consistent with the type of identifier that the 
> FunctionCatalog/CatalogManager accepts.
> Some methods accept {{UnresolvedIdentifier}} e.g. 
> {{FunctionCatalog#registerTemporaryCatalogFunction}}, 
> {{CatalogManager#dropTemporaryView}}. 
> Some resolved {{ObjectIdentifier}} e.g. 
> {{CatalogManager#createTemporaryTable}}, {{CatalogManager#createTable}}.
> I am not sure which one should we prefer. If we go with the 
> {{UnresolvedIdentifier}} the benefit is that we always qualify it in a 
> {{Catalog*}}. The downside is that we would use {{UnresolvedIdentifier}} in 
> {{*Operations}}, (e.g. {{CreateTableOperation}} etc.), whereas we said that 
> all Operations should be fully resolved...



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (FLINK-15859) Unify identifiers in the interface methods of CatalogManager

2021-06-04 Thread Flink Jira Bot (Jira) 


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

Flink Jira Bot updated FLINK-15859:
---
  Labels: auto-deprioritized-major  (was: stale-major)
Priority: Minor  (was: Major)

This issue was labeled "stale-major" 7 ago and has not received any updates so 
it is being deprioritized. If this ticket is actually Major, please raise the 
priority and ask a committer to assign you the issue or revive the public 
discussion.


> Unify identifiers in the interface methods of CatalogManager
> 
>
> Key: FLINK-15859
> URL: https://issues.apache.org/jira/browse/FLINK-15859
> Project: Flink
>  Issue Type: Improvement
>  Components: Table SQL / API
>Reporter: Dawid Wysakowicz
>Priority: Minor
>  Labels: auto-deprioritized-major
> Fix For: 1.14.0
>
>
> We're not being too consistent with the type of identifier that the 
> FunctionCatalog/CatalogManager accepts.
> Some methods accept {{UnresolvedIdentifier}} e.g. 
> {{FunctionCatalog#registerTemporaryCatalogFunction}}, 
> {{CatalogManager#dropTemporaryView}}. 
> Some resolved {{ObjectIdentifier}} e.g. 
> {{CatalogManager#createTemporaryTable}}, {{CatalogManager#createTable}}.
> I am not sure which one should we prefer. If we go with the 
> {{UnresolvedIdentifier}} the benefit is that we always qualify it in a 
> {{Catalog*}}. The downside is that we would use {{UnresolvedIdentifier}} in 
> {{*Operations}}, (e.g. {{CreateTableOperation}} etc.), whereas we said that 
> all Operations should be fully resolved...



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (FLINK-15859) Unify identifiers in the interface methods of CatalogManager

2021-05-27 Thread Flink Jira Bot (Jira) 


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

Flink Jira Bot updated FLINK-15859:
---
Labels: stale-major  (was: )

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 
Major but is unassigned and neither itself nor its Sub-Tasks have been updated 
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this 
ticket is a Major, please either assign yourself or give an update. Afterwards, 
please remove the label or in 7 days the issue will be deprioritized.


> Unify identifiers in the interface methods of CatalogManager
> 
>
> Key: FLINK-15859
> URL: https://issues.apache.org/jira/browse/FLINK-15859
> Project: Flink
>  Issue Type: Improvement
>  Components: Table SQL / API
>Reporter: Dawid Wysakowicz
>Priority: Major
>  Labels: stale-major
> Fix For: 1.14.0
>
>
> We're not being too consistent with the type of identifier that the 
> FunctionCatalog/CatalogManager accepts.
> Some methods accept {{UnresolvedIdentifier}} e.g. 
> {{FunctionCatalog#registerTemporaryCatalogFunction}}, 
> {{CatalogManager#dropTemporaryView}}. 
> Some resolved {{ObjectIdentifier}} e.g. 
> {{CatalogManager#createTemporaryTable}}, {{CatalogManager#createTable}}.
> I am not sure which one should we prefer. If we go with the 
> {{UnresolvedIdentifier}} the benefit is that we always qualify it in a 
> {{Catalog*}}. The downside is that we would use {{UnresolvedIdentifier}} in 
> {{*Operations}}, (e.g. {{CreateTableOperation}} etc.), whereas we said that 
> all Operations should be fully resolved...



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (FLINK-15859) Unify identifiers in the interface methods of CatalogManager

2021-04-02 Thread Jark Wu (Jira) 


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

Jark Wu updated FLINK-15859:

Fix Version/s: (was: 1.13.0)
   1.14.0

> Unify identifiers in the interface methods of CatalogManager
> 
>
> Key: FLINK-15859
> URL: https://issues.apache.org/jira/browse/FLINK-15859
> Project: Flink
>  Issue Type: Improvement
>  Components: Table SQL / API
>Reporter: Dawid Wysakowicz
>Priority: Major
> Fix For: 1.14.0
>
>
> We're not being too consistent with the type of identifier that the 
> FunctionCatalog/CatalogManager accepts.
> Some methods accept {{UnresolvedIdentifier}} e.g. 
> {{FunctionCatalog#registerTemporaryCatalogFunction}}, 
> {{CatalogManager#dropTemporaryView}}. 
> Some resolved {{ObjectIdentifier}} e.g. 
> {{CatalogManager#createTemporaryTable}}, {{CatalogManager#createTable}}.
> I am not sure which one should we prefer. If we go with the 
> {{UnresolvedIdentifier}} the benefit is that we always qualify it in a 
> {{Catalog*}}. The downside is that we would use {{UnresolvedIdentifier}} in 
> {{*Operations}}, (e.g. {{CreateTableOperation}} etc.), whereas we said that 
> all Operations should be fully resolved...



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (FLINK-15859) Unify identifiers in the interface methods of CatalogManager

2020-11-16 Thread Leonard Xu (Jira) 


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

Leonard Xu updated FLINK-15859:
---
Fix Version/s: (was: 1.12.0)
   1.13.0

> Unify identifiers in the interface methods of CatalogManager
> 
>
> Key: FLINK-15859
> URL: https://issues.apache.org/jira/browse/FLINK-15859
> Project: Flink
>  Issue Type: Improvement
>  Components: Table SQL / API
>Reporter: Dawid Wysakowicz
>Priority: Major
> Fix For: 1.13.0
>
>
> We're not being too consistent with the type of identifier that the 
> FunctionCatalog/CatalogManager accepts.
> Some methods accept {{UnresolvedIdentifier}} e.g. 
> {{FunctionCatalog#registerTemporaryCatalogFunction}}, 
> {{CatalogManager#dropTemporaryView}}. 
> Some resolved {{ObjectIdentifier}} e.g. 
> {{CatalogManager#createTemporaryTable}}, {{CatalogManager#createTable}}.
> I am not sure which one should we prefer. If we go with the 
> {{UnresolvedIdentifier}} the benefit is that we always qualify it in a 
> {{Catalog*}}. The downside is that we would use {{UnresolvedIdentifier}} in 
> {{*Operations}}, (e.g. {{CreateTableOperation}} etc.), whereas we said that 
> all Operations should be fully resolved...



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (FLINK-15859) Unify identifiers in the interface methods of CatalogManager

2020-06-02 Thread Danny Chen (Jira) 


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

Danny Chen updated FLINK-15859:
---
Fix Version/s: (was: 1.11.0)
   1.12.0

> Unify identifiers in the interface methods of CatalogManager
> 
>
> Key: FLINK-15859
> URL: https://issues.apache.org/jira/browse/FLINK-15859
> Project: Flink
>  Issue Type: Improvement
>  Components: Table SQL / API
>Reporter: Dawid Wysakowicz
>Priority: Major
> Fix For: 1.12.0
>
>
> We're not being too consistent with the type of identifier that the 
> FunctionCatalog/CatalogManager accepts.
> Some methods accept {{UnresolvedIdentifier}} e.g. 
> {{FunctionCatalog#registerTemporaryCatalogFunction}}, 
> {{CatalogManager#dropTemporaryView}}. 
> Some resolved {{ObjectIdentifier}} e.g. 
> {{CatalogManager#createTemporaryTable}}, {{CatalogManager#createTable}}.
> I am not sure which one should we prefer. If we go with the 
> {{UnresolvedIdentifier}} the benefit is that we always qualify it in a 
> {{Catalog*}}. The downside is that we would use {{UnresolvedIdentifier}} in 
> {{*Operations}}, (e.g. {{CreateTableOperation}} etc.), whereas we said that 
> all Operations should be fully resolved...



--
This message was sent by Atlassian Jira
(v8.3.4#803005)