iercan opened a new issue, #21567: URL: https://github.com/apache/superset/issues/21567
I have upgraded sqlalchemy-trino==0.4.1 to trino==0.315.0. After that we started getting below error  I did some investigation and realized superset started to set column type as timestamp(3) instead of timestamp after upgrade. This change prevent superset casts time correctly. I've compared queries and saw that superset does not cast time filter anymore. Casting before(working) `inserted_at >= from_iso8601_timestamp('2022-09-16T09:07:45.000000')` Casting after(erroneous) `inserted_at >= '2022-09-16 08:47:13.000000'` Clearly there is some compatibility issue with new trino client. For now I solved my problem by downgrading trino client but I'd appreciate If this issue solved so that we can use latest client #### How to reproduce the bug 1. Replace sqlalchemy-trino==0.4.1 with trino==0.315.0 2. Sync dataset(which have a timestamp column) columns 3. Send a query with time filter. ### Environment - superset version: 1.5.0 docker image ### Additional context Related #16223 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
