naming approach for hierarchy

I agree with using Hive-style partition naming when you actually need partition columns to be recognized by the engine.

One extra point is to avoid designing the folder hierarchy first and then forcing the Delta table to match it. In Fabric, I’d define the table partitioning strategy based on query patterns and data volume, then let Delta create the physical layout.

For lower-volume datasets, year/month/day can create too many small partitions, so testing year/month or even no traditional partitioning can be better. The main goal should be efficient pruning without creating excessive small files.