Re: TIME/TIMESTAMP parse in Flink TABLE/SQL API

2020-03-23 Thread Jark Wu
;>> > An implementation note. I think we should aim to base the >>>> implementation >>>> > on the DataTypes already rather than going back to the >>>> TypeInformation. >>>> > >>>> > I would still try to le

Re: TIME/TIMESTAMP parse in Flink TABLE/SQL API

2020-02-26 Thread Jingsong Li
QL >>> standard. >>> >> The problem is that JsonRowDeserializationSchema only support >>> RFC-3339. >>> >> On the other hand, CsvRowDeserializationSchema supports to parse >>> >> "2019-07-09 02:02:00.040". >>> >&

Re: TIME/TIMESTAMP parse in Flink TABLE/SQL API

2020-02-26 Thread Jark Wu
f the >> > standard as it makes time types unambiguous. >> > >> > What do you think? >> > >> > Ps. I cross posted this on the dev ML. >> > >> > Best, >> > >> > Dawid >> > >> > >> > On 26/02/

Re: TIME/TIMESTAMP parse in Flink TABLE/SQL API

2020-02-26 Thread Jingsong Li
awid > > > > > > On 26/02/2020 03:45, Jark Wu wrote: > > > > Yes, I'm also in favor of loosen the datetime format constraint. > > I guess most of the users don't know there is a JSON standard which > > follows RFC 3339. > > > > Best, > &

Re: TIME/TIMESTAMP parse in Flink TABLE/SQL API

2020-02-26 Thread Jark Wu
port “loosen it for usability”. If not, may add some explanation >> about JSON. >> >> >> >> Original Message >> *Sender:* Jark Wu >> *Recipient:* Outlook; Dawid Wysakowicz< >> dwysakow...@apache.org> >> *Cc:* godfrey he; Leonard

Re: TIME/TIMESTAMP parse in Flink TABLE/SQL API

2020-02-26 Thread Dawid Wysakowicz
.@outlook.com>>; Dawid > Wysakowiczmailto:dwysakow...@apache.org>> > *Cc:* godfrey he <mailto:godfre...@gmail.com>>; Leonard Xu <mailto:xbjt...@gmail.com>>; user <mailto:u...@flink.apache.org>> > *Date:* Wednesday, Feb 26, 2020 09