Properly initialize Iceberg REST catalog Configuration#16455
Properly initialize Iceberg REST catalog Configuration#16455alexjo2144 wants to merge 2 commits intotrinodb:masterfrom
Conversation
|
We either need to set it or change the FileIO implementation that's being used. Because we delegate to the core Iceberg library for the In the other TrinoCatalog implementations we use |
|
We should fix it to use |
|
I looked through the code and there doesn't seem to be an obvious way to add it here. We might be able to do it by subclassing For now, we might need to fork
|
|
@electrum how would you feel about merging this fix for now and getting ForwardingFileIO into here and JDBC after? The rest catalog is completely broken as is. |
|
@alexjo2144 You can set the Catalog FileIO via the RESTSessionCatalog initialization here properties.put(CatalogProperties.FILE_IO_IMPL, ForwardingFileIO.class.getName()) |
|
Thanks Dan, I saw that but the ForwardingFileIO takes a |
|
I see, we can use ForwardingFileIO today if we implement |
If the `hive.fs.cache.max-size` property is set to zero the first time a FileSystem is loaded an exception is thrown "FileSystem max cache size has been reached"
7f5a4e5 to
af3c168
Compare
|
@dain and I had a call with @rdblue and @danielcweeks this morning. Ryan is going to propose an API change Iceberg 1.2.0 for the catalogs that lets us provide a |
|
We'll be able to fix this with Iceberg 1.2.0 thanks to apache/iceberg#7064 |
af3c168 to
944892a
Compare
|
Thanks David, if you'd rather wait for that fix in 1.2.0 I'll go ahead and close this |
Description
Without these configurationInitializers catalog properties are not properly sent to the file system implementation.
Additional context and related issues
#13294
Release notes
( ) This is not user-visible or docs only and no release notes are required.
(x) Release notes are required, please propose a release note for me.
( ) Release notes are required, with the following suggested text: