Forum Discussion
Lakehouse Table Mapping Unidentified
- 7 months ago
Hello JDay98
The issue with schema shortcuts is typically caused by:
- A corrupted or partially synchronised schema metadata file
- Modifications to the underlying Delta transaction log at the source
- Desynchronisation of shortcuts following schema evolution
- Inconsistent metadata within the mirrored lakehouse
Before addressing your mirrored lakehouse, please ensure the source is in good health.
Within your production lakehouse, confirm that /Tables exists and contains the *_delta_log:
Fabric shortcuts may have become outdated.
To refresh:
- Select the relevant schema shortcut
- Click Refresh
If the refresh is unsuccessful, it is likely due to metadata corruption in either the shortcut or the source.
From the mirrored lakehouse:
- Go to SQL Endpoint → Refresh
- Navigate to Tables view → Refresh
- If the problematic table displays a warning, select “Remove from SQL endpoint”
This action removes only the metadata and does not affect the actual data.
Hello JDay98
The issue with schema shortcuts is typically caused by:
- A corrupted or partially synchronised schema metadata file
- Modifications to the underlying Delta transaction log at the source
- Desynchronisation of shortcuts following schema evolution
- Inconsistent metadata within the mirrored lakehouse
Before addressing your mirrored lakehouse, please ensure the source is in good health.
Within your production lakehouse, confirm that /Tables exists and contains the *_delta_log:
Fabric shortcuts may have become outdated.
To refresh:
- Select the relevant schema shortcut
- Click Refresh
If the refresh is unsuccessful, it is likely due to metadata corruption in either the shortcut or the source.
From the mirrored lakehouse:
- Go to SQL Endpoint → Refresh
- Navigate to Tables view → Refresh
- If the problematic table displays a warning, select “Remove from SQL endpoint”
This action removes only the metadata and does not affect the actual data.