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 <trohrm...@apache.org> wrote: > 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. > > Cheers, > Till > > On Mon, Mar 16, 2020 at 5:48 AM <b.z...@dell.com> wrote: > >> 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 conversion error >> in the Timestamp with our descriptor Table API. The detail is in the issue >> here: https://github.com/pravega/flink-connectors/issues/341 Hope >> someone from Flink community can help us with some suggestions on this >> issue. Thanks. >> >> >> >> Best Regards, >> >> Brian >> >> >> >
