microsoft / microsoft/Dynamics-365-FastTrack-Implementation-Assets
Undocumented Change in CDM Utils that Impacts funemental operation
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 494
- Forks
- 296
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 5
Description
When the DDL Type was set to SynapseTable:, in earlier versions, upon table activation or a schema change, CDM Utils would automatically drop the table and recreate it. In the current version, it appears to check if the table exists and only drop and create the table if it doesn't exist.
Because of this issue, if there is a table metadata change- the synapse table in the dedicated pool no longer reflects the most current table metadata.
The option is needed to Drop/Create automatically as per all prior versions.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the CDM Utils handling for the DDL Type SynapseTable and compare the current table-existence check with the behavior in earlier versions. Verify activation and schema changes in a dedicated pool, and consider the issue complete when table metadata is updated through the requested automatic drop-and-recreate behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100