Timo Walther
Sent: Tuesday, March 24, 2020 16:40
To: Zhou, Brian; imj...@gmail.com
Cc: user@flink.apache.org
Subject: Re: Need help on timestamp type conversion for Table API on Pravega
Connector
[EXTERNAL EMAIL]
This issue is tracked under:
https://issues.apache.org/jira/browse/FLINK-1
o/pravega/connectors/flink/FlinkPravegaTableITCase.java#L310
Best Regards,
Brian
*From:* Jark Wu
*Sent:* Thursday, March 19, 2020 20:25
*To:* Till Rohrmann
*Cc:* Zhou, Brian; Timo Walther; Jingsong Li; user
*Subject:* Re: Need help on timestamp type conversion for Table API on
Pravega Connect
mann
Cc: Zhou, Brian; Timo Walther; Jingsong Li; user
Subject: Re: Need help on timestamp type conversion for Table API on Pravega
Connector
[EXTERNAL EMAIL]
This maybe a similar issue to [1], we continue the discussion there.
Best,
Jark
[1]:
http://apache-flink-user-mailing-list-archive.23360
This maybe a similar issue to [1], we continue the discussion there.
Best,
Jark
[1]:
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/SQL-Timetamp-types-incompatible-after-migration-to-1-10-td33784.html#a33791
On Tue, 17 Mar 2020 at 18:05, Till Rohrmann wrote:
> Thanks for
Thanks for reporting this issue Brian. I'm not a Table API expert but I
know that there is some work on the type system ongoing. I've pulled Timo
and Jingsong into the conversation who might be able to tell you what
exactly changed and whether the timestamp issue might be caused by the
changes.
Ch
Hi community,
Pravega connector is a connector that provides both Batch and Streaming Table
API implementation. We uses descriptor API to build Table source. When we plan
to upgrade to Flink 1.10, we found the unit tests are not passing with our
existing Batch Table API. There is a type convers
