# Does Trino Support Iceberg Tables stored in azure with both "abfs\[s\]" and "wasb\[s\]" present in the metadata?

**URL:** <https://www.starburst.io/community/forum/t/does-trino-support-iceberg-tables-stored-in-azure-with-both-abfs-s-and-wasb-s-present-in-the-metadata/598>\
**Category:** Trino\
**Tags:** iceberg\
**Created:** [October 31, 2024, 8:06pm UTC](https://www.starburst.io/community/forum/t/does-trino-support-iceberg-tables-stored-in-azure-with-both-abfs-s-and-wasb-s-present-in-the-metadata/598 "2024-10-31T20:06:01Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jordano](https://www.starburst.io/community/forum/letter_avatar_proxy/v4/letter/j/34f0e0/32.png) [@Jordano](https://www.starburst.io/community/forum/u/Jordano)\
**Post date:** [October 31, 2024, 8:06pm UTC](https://www.starburst.io/community/forum/t/does-trino-support-iceberg-tables-stored-in-azure-with-both-abfs-s-and-wasb-s-present-in-the-metadata/598/1 "2024-10-31T20:06:01Z")

</div>

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:

```auto
wasbs://containername@accountname.blob.core.windows.net

```

```auto
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?