[RESULT][VOTE] FLIP-463: Schema Definition in CREATE TABLE AS Statement

Hi everyone, the vote [1] for FLIP-463 [2] is over. The number of required binding votes (3) was reached (total: 8, binding: 3, non-binding: 5). Binding - Timo Walther - Sergey Nuyanzin - Martijn Visser Non-binding - Ferenc Csaky - Jeyhun Karimov - Jim Hughes - Yanquan Lv - Zhongqiang Gong There

[VOTE] FLIP-463: Schema Definition in CREATE TABLE AS Statement

Hi everyone, Thanks for all the feedback about FLIP-463: Schema Definition in CREATE TABLE AS Statement [1]. The discussion thread is here [2]. I'd like to start a vote for it. The vote will be open for at least 72 hours unless there is an objection or insufficient votes. The FLIP will be conside

Re: [DISCUSS] FLIP-463: Schema Definition in CREATE TABLE AS Statement

| INT | NULL || +-+---+--++ Let me know your thoughts. - Sergio On Tue, Jun 18, 2024 at 7:34 AM Sergio Pena wrote: > Hi Ron, > > I think the primary key and unique values are handled by the engine. I > found this document [1

Re: [DISCUSS] FLIP-463: Schema Definition in CREATE TABLE AS Statement

the data fetched > by the Select query can't guarantee uniqueness based on column a, then what > is relied upon to ensure uniqueness? > Is it something that the engine does, or is it dependent on the storage > mechanism of the target table? > > Best, > Ron > > > Sergio

Re: [DISCUSS] FLIP-463: Schema Definition in CREATE TABLE AS Statement

6月14日周五 01:51写道： > > > Thanks Sergio and Timo for your answers. > > Sounds good to me. > > Looking forward for this feature. > > > > Regards, > > Jeyhun > > > > On Thu, Jun 13, 2024 at 4:48 PM Sergio Pena > > > wrote: > > > > >

Re: [DISCUSS] FLIP-463: Schema Definition in CREATE TABLE AS Statement

ts: > > 1. If we have a source table with primary keys and partition keys > defined, > > what is the default behavior if PARTITIONED and DISTRIBUTED not specified > > in the CTAS statement, It should not be inherited by default？ > > 2. I suggest providing a complete synta

Re: [DISCUSS] FLIP-463: Schema Definition in CREATE TABLE AS Statement

be inherited by default？ > 2. I suggest providing a complete syntax that includes table_properties > like FLIP-218. > > > Sergio Pena 于2024年6月12日周三 03:54写道： > > > I just noticed the CREATE TABLE LIKE statement allows the definition of > new > > columns in the CREA

Re: [DISCUSS] FLIP-463: Schema Definition in CREATE TABLE AS Statement

LE LIKE? Seems the best approach in order to be compatible with it. - Sergio On Tue, Jun 11, 2024 at 2:10 PM Sergio Pena wrote: > Thanks Timo for answering Jeyhun questions. > > To add info more about your questions Jeyhun. This proposal is not > handling NULL/NOT_NULL types. I notice

Re: [DISCUSS] FLIP-463: Schema Definition in CREATE TABLE AS Statement

FLIP for this case? > > - In some cases, redefining the column types might be redundant, > especially > > when users dont change the column type. For example, a user just wants to > > change the column name from the SELECT clause. > > Should we also support this scenario, similar

Re: [DISCUSS] FLIP-463: Schema Definition in CREATE TABLE AS Statement

://docs.aws.amazon.com/athena/latest/ug/ctas-considerations-limitations.html#ctas-considerations-limitations-order-by-ignored > > > Kind regards, David. > > From: Sergio Pena > Date: Friday, 7 June 2024 at 16:13 > To: dev@flink.apache.org > Subject: [EXTERNAL] [DISC

[DISCUSS] FLIP-463: Schema Definition in CREATE TABLE AS Statement

ughts are welcome. Thanks, - Sergio Pena [1] https://cwiki.apache.org/confluence/display/FLINK/FLIP-463%3A+Schema+Definition+in+CREATE+TABLE+AS+Statement