microsoft / microsoft/Dynamics-365-FastTrack-Implementation-Assets
In the DataLakeToSQLCopy pipeline, archiving change feed files
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 494
- Forks
- 296
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 5
Description
Do we really need to keep the archiving delete activity in the pipeline DataLakeToSQLCopy?
Aren't these files taken based on the lastcopydatetime? (based on the checkfornewfiles activity within the same for each loop)
I'm thinking of removing the ArchiveChangeFeed activity. It shouldn't affect the merge of cdc files right?
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
Inspect the DataLakeToSQLCopy pipeline, focusing on the checkfornewfiles activity, lastcopydatetime handling, ArchiveChangeFeed, and the merge of CDC files. Verify whether removing ArchiveChangeFeed preserves file selection and merge behavior; done means reaching a clear decision supported by pipeline validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- data-engineering, databases
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100