Does anyone know if there's a way to specify an alternate Unity schema in a DLT workflow using the @Dlt.table syntax? In my case, Iโm looping through folders in Azure datalake storage to ingest data. Iโd like those folders to get created in different schemas within a single (or multiple) unity catalog.
For example:
- Catalog1 : schemaA : tableA
- Catalog1 : schemaB : tableB
- Catalog2 : schemaC : tableC
I tried specifying the 3 dot nomenclature in the table name in my @Dlt.table syntax and received an error โINVALID_PARAMETER_VALUE.INVALID_FIELD CreateStagingTable name is not a valid name.โ Specifying the โpathโ attribute also returns an error that I canโt do that with Unity. When creating the workflow Iโm allowed to leave the schema blank but I canโt figure out how to specify it in my code.
Iโve been googling around for a couple days and couldnโt find an answer. Would love if you could suggest a solution that didnโt involve having to create separate workflows for each schema.