Open iuliu-b opened 2 months ago
Ah, okay I think this calls for a refactoring. At this point there are a few catalog options and I need to add REST to this catalog and I'll see if there are upstream issues going on or if there was a change in the configuration for HMS I need to figure out.
Thanks for continuing to report this! @tschaub also thanks for removing the other config that was breaking everything :) I need to reconsider how I manage these configs at some point. It would be nice to create a primary template that would allow for extra properties for each subproject.
I think a setup like this would be beneficial with a tutorial on catalogs.
@bitsondatadev
I'll see if there are upstream issues going on or if there was a change in the configuration for HMS I need to figure out
Correct me if I'm wrong - seems like the HMS image is fixed at 3.0.0
(this project's compose file is targeting bitsondatadev/hive-metastore:latest
, but bitsondatadev/hive-metastore
itself has 3.0.0
hardcoded) - so HMS configuration couldn't have changed?
Asking because I'd love to have a working version of trino-minio
to play around with, and am wondering if the answer is to walk back through the package versions of the latest
depedencies (trinodb/trino:latest
, mariadb:latest
, minio/minio:latest
) until I reach a working hardcoded version set)
I think the root cause is this issue https://github.com/sysown/proxysql/issues/3017
and the project works fine using mariadb:10.6.16
After pulling the latest version I'm getting a failure different from https://github.com/bitsondatadev/trino-getting-started/issues/45 Edit: scratch that, see extended stack trace: it's the same error as before