Forum Discussion
Brackets in tablenames
- 1 month ago
Hi mstoegerer ,
Thank you for the additional details.
Based on your testing, the tables are being created successfully as Delta tables because they remain accessible through both Spark notebooks and the SQL analytics endpoint. However, when brackets or spaces are included in the table name, Lakehouse Explorer classifies them under Unidentified instead of displaying them in the Tables section.
According to the Lakehouse Explorer documentation, the Unidentified area is used for items that Fabric cannot properly recognize as valid tables. I could not find anything in the Lakehouse Explorer documentation that specifically states brackets or spaces should cause Delta tables to appear under Unidentified
Since this previously worked and the issue appears reproducible only for tables containing brackets or spaces, this may indicate a recent metadata recognition or UI regression in Lakehouse Explorer.Could you also confirm whether the issue occurs in a newly created Lakehouse and whether both existing and newly created bracketed table names are affected?
For Reference: Navigate the Fabric Lakehouse explorer - Microsoft Fabric | Microsoft LearnBest Regards,
Abdul Rafi
Hi mstoegerer ,
Thank you for reaching out to Microsoft Fabric Community and thanks to rajendraongole1 for sharing meaningful insights.
According to the Microsoft documentation, the Unidentified section in Lakehouse Explorer is used for items that Fabric cannot recognize as valid Delta tables, such as broken shortcuts, non-Delta content written to the Tables area, or folders that do not follow the expected Delta table structure
Could you please confirm:
- Whether these tables were created through the Lakehouse UI, Notebook, Data Pipeline, or another method?
- If newly created tables with simple names (without spaces or brackets) appear correctly?
- Whether the issue affects all tables or only specific ones?
- If you can access the tables through Spark notebooks or the SQL analytics endpoint?
The documentation does not indicate that spaces or brackets in table names should cause tables to appear under Unidentified, so gathering the above details will help narrow down whether this is related to table metadata, table creation method, or another issue.
For Reference:
Navigate the Fabric Lakehouse explorer - Microsoft Fabric | Microsoft Learn
Best Regards,
Abdul Rafi
Hi,
Thanks for you reply.
The tables were created in a notebook with following code:
df_fixed
.write
.format("delta")
.mode("overwrite")
.option("mergeSchema", "true")
.saveAsTable(table_name)That worked until recently quite well.
If I create a table with this code, without brackets, the table appears correctly under tables.
I can access the "unidentified" tables with spark and the SQL endpoint.
Best regards,
Markus
- v-moharafi-msft1 month agoCommunity Support
Hi mstoegerer ,
Thank you for the additional details.
Based on your testing, the tables are being created successfully as Delta tables because they remain accessible through both Spark notebooks and the SQL analytics endpoint. However, when brackets or spaces are included in the table name, Lakehouse Explorer classifies them under Unidentified instead of displaying them in the Tables section.
According to the Lakehouse Explorer documentation, the Unidentified area is used for items that Fabric cannot properly recognize as valid tables. I could not find anything in the Lakehouse Explorer documentation that specifically states brackets or spaces should cause Delta tables to appear under Unidentified
Since this previously worked and the issue appears reproducible only for tables containing brackets or spaces, this may indicate a recent metadata recognition or UI regression in Lakehouse Explorer.Could you also confirm whether the issue occurs in a newly created Lakehouse and whether both existing and newly created bracketed table names are affected?
For Reference: Navigate the Fabric Lakehouse explorer - Microsoft Fabric | Microsoft LearnBest Regards,
Abdul Rafi- mstoegerer1 month agoFrequent Visitor
Hello,
I wasn't able to test it more in detail in the last days.
I'll check it with a newly created Lakehouse in the next days and come back with the results.Best regards,
Markus
- v-kathullac1 month agoCommunity Support
Hi mstoegerer ,
Thaankyou for the confirmation. Could you please test the newly created Lakehouse and let us know if you encounter any further issues?
As of now, we will proceed with closing this thread . if you experience any issues in the future, please don't hesitate to create a new thread, and we will be happy to assist you.
Thank you for your cooperation.
Thanks,
Chaithanya.