-
Notifications
You must be signed in to change notification settings - Fork 240
Fix PathNotFound error in msexports ETL ingestion on first run #2247
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: flanakin/v15-prep
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -1694,6 +1694,7 @@ resource pipeline_ExecuteIngestionETL 'Microsoft.DataFactory/factories/pipelines | |
| } | ||
| } | ||
| fieldList: [ | ||
| 'exists' | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This changes which error the user gets, but the pipeline still fails on a missing folder. When So the cascade into If a first-run / no-data folder should be a no-op,
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Partly retracting this. I checked how the pipeline is invoked: What the hunk does change is which failure surfaces when the folder genuinely is missing — removed between trigger and run, or a
I'll take that as an improvement rather than a regression — a defined The one thing I'd still ask for is in the description rather than the code. It says the fix is applied "in both places this pattern exists", which reads as though both were failing the same way. They aren't: Exports writes to a destination folder that legitimately may not exist yet, Analytics reads a source folder a manifest just landed in. A sentence noting the Analytics change is diagnostic rather than a fix would stop the next person concluding that a missing ingestion folder is now a no-op there. Non-blocking. |
||
| 'childItems' | ||
| ] | ||
| storeSettings: { | ||
|
|
@@ -1720,7 +1721,7 @@ resource pipeline_ExecuteIngestionETL 'Microsoft.DataFactory/factories/pipelines | |
| userProperties: [] | ||
| typeProperties: { | ||
| items: { | ||
| value: '@if(contains(activity(\'Get Existing Parquet Files\').output, \'childItems\'), activity(\'Get Existing Parquet Files\').output.childItems, json(\'[]\'))' | ||
| value: '@if(and(activity(\'Get Existing Parquet Files\').output.exists, contains(activity(\'Get Existing Parquet Files\').output, \'childItems\')), activity(\'Get Existing Parquet Files\').output.childItems, json(\'[]\'))' | ||
| type: 'Expression' | ||
| } | ||
| condition: { | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.