CATALOG_NOT_FOUND errors on insert statements with Iceberg connector with Glue & S3 #23418
Closed
peterklingelhofer
started this conversation in
General
Replies: 1 comment
-
The issue was that the Trino workers were not getting the latest catalog config via |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We're seeing
CATALOG_NOT_FOUND
errors from Trino when we attempt INSERT statements. SELECT and CREATE TABLE statements work successfully (the select statement works when we grab data that was already inserted via AWS Athena, as Trino data insertion does not work here yet). When we runSHOW CATALOGS
, we rightly seeAvailable catalogs: [['glue'], ['system'], ['tpcds'], ['tpch']]
, and when we runSHOW SCHEMAS IN glue
we rightly seeAvailable schemas in glue: [['default'], ['information_schema'], ['test_database']]
. Select statements work successfully and grab data from the source. Table creation works fine, as does creating new databases. This service worker's Role ARN has access to all S3 resources withs3:*
andglue:*
.Weirdly, when I change the commit type to IsolationLevel.READ_COMMITTED, we see
Catalog only supports writes using autocommit: glue
(which tells me the catalog is indeed present...).Any ideas? Example code:
Trino helm chart values overrides (using Trino helm chart
0.28.0
):(including the
hive.metastore.glue
properties does not seem to have any effect on this catalog not found error)Beta Was this translation helpful? Give feedback.
All reactions