lpoulain
lpoulain
I received the same error when using the Python 3-based Anaconda. Switching to the Python 2 version got rid of this error (I have another error but that's another story)
@hashhar done.
Closing PR as too many things have changed since. Will file a new PR
After some further review, it turns out that the behavior seen is the correct one. Indeed, if we consider the first two columns: - Starburst returns the exact same timestamp...
@cobour switching to 1.8.2 indeed works, thanks!
Do you mean using an SSL self-signed cert stored on the machine where Metabase is running? i.e. allow to configure the Trino JDBC driver `SSLTrustStorePath` optional parameter.
@atekin I was not able to reproduce this error despite looking at a table with a JSON type. Could you provide the steps to get the error you mentioned?
I tried a large column with more than 1234 characters but couldn't reproduce the problem. And when I look at the SQL being generated by Metabase, I never see the...
I tried running this query using the Metabase Starburst Driver version 6.1.0 and could not reproduce the issue.
What actual query is executed on Trino? Is it this exact same query or a different one?