trino 351 no longer works with metabase

[wccropper]

upgraded prestoql 347 to trino 351 and metabase can no longer connect. The error message is

Catalog must be specified when session catalog is not set

This is the same message we received when using the older 347 cli to connect to the 351 db.

Opened a metabase discourse topic here

[wccropper]

Metabase has replied on the discourse link above and it looks like a new Trino API driver might be the best way to move forward in the short term and maybe eventually a JDBC implementation that would allow for the users to bring in the latest JDBC release themselves. This is of great importance to our company as we look towards Starburst compatibility as well.

[findepi]

You may need to use

protocol.v1.alternate-header-name=Presto

until metabase code is updated for Trino. let me know if it works.

[wccropper]

We will try this next. We would still like to see the Trino option added and kept up to date as Trino iterates so quickly.

[findepi]

I'm all for it. Would you consider opening relevant issue with Metabase for this?

[zifeo]

@findepi workaround works. What are the plans in the future to have a "dedicated" Trino driver in Metabase?

[findepi]

@zifeo that would be up to Metabase project, but there is a PR for this already -- metabase/metabase#15160

[soheildsh]

protocol.v1.alternate-header-name=Presto

where should I add this line of code in order to work? which file?

[kokosing]

Please place it in config.properties file.

[soheildsh]

Thank you sir. But when I place this line in config file when I run trino 351 I get the following error between many lines that are being printed on terminal:

trino_1  | ==========
trino_1  | 
trino_1  | Configuration should be updated:
trino_1  | 
trino_1  | 1) Configuration property 'protocol.v1.alternate-header-name' is deprecated and should not be used
trino_1  | 
trino_1  | ==========

and at the end of terminal it appears that trino cannot start showing this:

...
trino_1  | 2021-07-26T11:07:21.143Z     ERROR   Announcer-4     io.airlift.discovery.client.Announcer   Service announcement failed after 3.95ms. Next request will happen within 1000.00ms
trino_1  | 2021-07-26T11:07:22.148Z     ERROR   Announcer-0     io.airlift.discovery.client.Announcer   Service announcement failed after 3.94ms. Next request will happen within 1000.00ms
...

[rubenssoto]

Hello guys,

Do you have any solution on this?
We want to use Trino with metabase too.

I created an issue, please vote!

metabase/metabase#17532

[fazz21]

@rubenssoto & @wccropper does this problem could be solved temporarily with downgrade the trino version to 350 ? before prestosql change into trino. Because it is start to use trino-jdbc and also for the metabase version, it cannot be upgraded to metabase 0.41 because metabase 0.41 also apply presto-jdbc within the connection.

[ipleten]

To the one who's looking how to connect AWS EMR's Trino to AWS QuickSight workaround above works.
Thank you!

[paoliniluis]

Hi, check https://github.com/paoliniluis/metabase-trino, as Metabase and Trino works with the Starburst driver