When connecting to an apache iceberg table through Azure Object Storage, the table’s metadata and manifest locations will appear in one of the following formats:
wasbs://containername@accountname.blob.core.windows.net
abfss://containername@accountname.dfs.core.windows.net
The community strongly prefers users and engines to use the abfs[s] driver + .dfs. endpoint. However, some engines still write wasb[s]. This means that multi-engine writing on an iceberg table may cause metadata references to both abfs[s] and wasb[s]. Does Trino support reads on iceberg tables with both schemes present across various snapshots?