;>> > 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
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".
>>> >&
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/
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,
> &
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
.@outlook.com>>; Dawid
> Wysakowiczmailto:dwysakow...@apache.org>>
> *Cc:* godfrey he <mailto:godfre...@gmail.com>>; Leonard Xu <mailto:xbjt...@gmail.com>>; user <mailto:user@flink.apache.org>>
> *Date:* Wednesday, Feb 26, 2020 09
ntics are closer to {@link java.time.LocalTime}. A time WITH time
>> zone is not provided.
>> *
>> * @see #TIME(int)
>> * @see TimeType
>> */
>> public static DataType TIME() {
>> return new AtomicDataType(new TimeType());
>>
>> }```
>>
>&
Subject: Re: TIME/TIMESTAMP parse in Flink TABLE/SQL API
Hi Outlook,
The explanation in DataTypes is correct, it is compliant to SQL standard. The
problem is that JsonRowDeserializationSchema only support RFC-3339.
On the other hand, CsvRowDeserializationSchema supports to parse "2019-
>
>
> Thanks again.
>
> Original Message
> *Sender:* Leonard Xu
> *Recipient:* godfrey he
> *Cc:* Outlook; user
> *Date:* Tuesday, Feb 25, 2020 22:56
> *Subject:* Re: TIME/TIMESTAMP parse in Flink TABLE/SQL API
>
> Hi，Outlook
> Godfrey is righ
again.
Original Message
Sender: Leonard Xu
Recipient: godfrey he
Cc: Outlook; user
Date: Tuesday, Feb 25, 2020 22:56
Subject: Re: TIME/TIMESTAMP parse in Flink TABLE/SQL API
Hi，Outlook
Godfrey is right, you should follow the json format[1] when you parse your json
message.
You can use foll
ecipient: usermailto:user@flink.apache.org>>
> Date: Tuesday, Feb 25, 2020 17:43
> Subject: TIME/TIMESTAMP parse in Flink TABLE/SQL API
>
> Hi all,
>
> I read json data from kafka, and print to console. When I do this, some error
> occurs when time/timestamp deserialization
my flink version is 1.10.0.
>
> Original Message
> *Sender:* Outlook
> *Recipient:* user
> *Date:* Tuesday, Feb 25, 2020 17:43
> *Subject:* TIME/TIMESTAMP parse in Flink TABLE/SQL API
>
> Hi all,
>
> I read json data from kafka, and print to console. When I do th
By the way, my flink version is 1.10.0.
Original Message
Sender: Outlook
Recipient: user
Date: Tuesday, Feb 25, 2020 17:43
Subject: TIME/TIMESTAMP parse in Flink TABLE/SQL API
Hi all,
I read json data from kafka, and print to console. When I do this, some error
occurs when time/timestamp
Hi all,
I read json data from kafka, and print to console. When I do this, some error
occurs when time/timestamp deserialization.
json data in Kafka:
```
{
"server_date": "2019-07-09",
"server_time": "14:02:00",
"reqsndtime_c": "2019-07-09 02:02:00.040"
}
```
flink code:
```
bsTableEnv.c
14 matches
Mail list logo
