microsoft / microsoft/Dynamics-365-FastTrack-Implementation-Assets
DataLakeToSQL_Export pipeline fails due to NullRef exception in getManifestDetails function.
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 494
- Forks
- 296
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 5
Description
ManifestReader.ListBlobs is hard coded to return null. This causes the function to throw NullRef exception
foreach (var manifest in c.AdlsContext.ManifestDefinitions)
{
manifestDefinitions = await ManifestReader.listBlob(c, manifest.ManifestLocation, log);
}
listBlob method is totally commented out and hard coded to return null. Trying to uncomment it surfaces a number of other compilation issues.
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
Start in Analytics/CDMUtilSolution/CDMUtil/Manifest/ManifestHandler.cs at the getManifestDetails call and the commented-out listBlob method. Review the compilation issues that appear when listBlob is uncommented, then run the DataLakeToSQL_Export pipeline or its available tests. Done means manifest listing no longer returns null and the pipeline avoids the reported NullRef exception.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100