Hi all, Sorry for the late reply.
>table.cor-table-as-select.atomicity-enabled Regarding `cor`, this abbreviation is not commonly used. >Create Table As Select(CTAS) feature depends on the serializability of the >catalog. To quickly see if the catalog supports CTAS, we need to try to >serialize the catalog when compile SQL in planner and if it fails, an >exception will be >thrown to indicate to user that the catalog does not >support CTAS because it cannot be serialized. This behavior is too cryptic, and will break the current catalog behavior when using 1.16. I suggest we introduce a new interface for atomic catalog which implements Serializable. The existent catalogs can choose whether implements the new catalog interface. > Catalog#inferTableOptions I strongly recommend not introducing this feature now, because the behavior is unclear. 1) if the catalog support managed table, the connector option is empty. but if user forget to set connector option for CTAS statement, the created table will be managed table. 2) the options and its values for catalog and for connector may be different, so use the catalog option may cause expected errors. > StreamGraph#addJobStatusHook I prefer `registerJobStatusHook` Best, Godfrey Mang Zhang <zhangma...@163.com> 于2022年6月13日周一 16:43写道： > > Hi Yun, > Thanks for your reply! > Through offline communication with Dalong, I updated the JobStatusHook part > to FLIP, looking forward to your feedback. > > > > -- > > Best regards, > Mang Zhang > > > > > > At 2022-05-31 14:34:25, "Yun Gao" <yungao...@aliyun.com.INVALID> wrote: > >Hi, > > > >Regarding the drop operation, with some offline discussion with Dalong and > >Zhu, > >we think that listening in the client side might be problematic since it > >would exit > >after submitting the jobs in detached mode, thus the operation might need to > >be in the JobMaster side. > > > >For the listener interface, currently JobListener only resides in the client > >side > >and contains unsuitable methods like onJobSubmitted for this scenario, and > >the internal JobStatusListener is designed to be used inside JM and is not > >serializable, thus we tend to add a new interface JobStatusHook, > >which could be attached to the JobGraph and executed in the JobMaster. > >The interface will also be marked as Internal. > > > >Best, > >Yun > > > > > >------------------------------------------------------------------ > >From:Mang Zhang <zhangma...@163.com> > >Send Time:2022 May 25 (Wed.) 10:24 > >To:dev <dev@flink.apache.org> > >Subject:Re:Re: [DISCUSS] FLIP-218: Support SELECT clause in CREATE > >TABLE(CTAS) > > > >Hi, Martijn > >Thanks for your reply! > >I looked at the SQL standard, CTAS is part of the SQL standard. > >Feature T172 is "AS subquery clause in table definition". > > > > > > > >-- > > > >Best regards, > >Mang Zhang > > > > > > > > > > > >At 2022-05-04 21:49:00, "Martijn Visser" <martijnvis...@apache.org> wrote: > >>Hi everyone, > >> > >>Can we identify if this proposed syntax is part of the SQL standard? > >> > >>Best regards, > >> > >>Martijn Visser > >>https://twitter.com/MartijnVisser82 > >>https://github.com/MartijnVisser > >> > >> > >>On Fri, 29 Apr 2022 at 11:19, yuxia <luoyu...@alumni.sjtu.edu.cn> wrote: > >> > >>> Thanks for for driving this work, it's to be a useful feature. > >>> About the flip-218, I have some questions. > >>> > >>> 1: Does our CTAS syntax support specify target table's schema including > >>> column name and data type? I think it maybe a useful fature in case we > >>> want > >>> to change the data types in target table instead of always copy the source > >>> table's schema. It'll be more flexible with this feature. > >>> Btw, MySQL's "CREATE TABLE ... SELECT Statement"[1] support this feature. > >>> > >>> 2: Seems it'll requre sink to implement an public interface to drop table, > >>> so what's the interface will look like? > >>> > >>> [1] https://dev.mysql.com/doc/refman/8.0/en/create-table-select.html > >>> > >>> Best regards, > >>> Yuxia > >>> > >>> ----- 原始邮件 ----- > >>> 发件人: "Mang Zhang" <zhangma...@163.com> > >>> 收件人: "dev" <dev@flink.apache.org> > >>> 发送时间: 星期四, 2022年 4 月 28日 下午 4:57:24 > >>> 主题: [DISCUSS] FLIP-218: Support SELECT clause in CREATE TABLE(CTAS) > >>> > >>> Hi, everyone > >>> > >>> > >>> I would like to open a discussion for support select clause in CREATE > >>> TABLE(CTAS), > >>> With the development of business and the enhancement of flink sql > >>> capabilities, queries become more and more complex. > >>> Now the user needs to use the Create Table statement to create the target > >>> table first, and then execute the insert statement. > >>> However, the target table may have many columns, which will bring a lot of > >>> work outside the business logic to the user. > >>> At the same time, ensure that the schema of the created target table is > >>> consistent with the schema of the query result. > >>> Using a CTAS syntax like Hive/Spark can greatly facilitate the user. > >>> > >>> > >>> > >>> You can find more details in FLIP-218[1]. Looking forward to your > >>> feedback. > >>> > >>> > >>> > >>> [1] > >>> https://cwiki.apache.org/confluence/display/FLINK/FLIP-218%3A+Support+SELECT+clause+in+CREATE+TABLE(CTAS) > >>> > >>> > >>> > >>> > >>> -- > >>> > >>> Best regards, > >>> Mang Zhang > >>> > >
