ADF skip and log incompatible rows - always creates empty file

O'Flynn, Kieran 36 Reputation points
2022-04-27T13:59:14.487+00:00

We have a number of ADF pipelines with copy activities that load raw data files into Azure SQL Paas DB's or Azure DWH staging tables.

We have "skip incompatible rows" fault tolerance switched on, and we are logging the skipped rows to blob storage rejection files. Logging level is "Warning" and logging mode is "Reliable".

We have found that this always creates a reject file in the blob storage container. The file will be empty except for the ADF column headers (see image).
197054-image.png

Is there any way to avoid creating these empty files while still having this logging capability?

Azure SQL Database
Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
11,639 questions
0 comments No comments
{count} votes

Accepted answer
  1. AnnuKumari-MSFT 34,556 Reputation points Microsoft Employee Moderator
    2022-04-28T18:51:16.55+00:00

    Hi @O'Flynn, Kieran ,
    Welcome to Microsoft Q&A platform and thankyou for posting your query.
    As I understand your question here, you want to know if there is any way to avoid the creation of empty files generated as a result of no warnings for skip incompatible rows option.

    Unfortunately, even if there is no warning to be captured the files would be generated . That's how it works right now.

    However, let me collaborate with the internal product team to find out if there is any future plan to just avoid the creation of files if there is no warning . I will keep you posted once I hear back from them . Thanks for your patience!

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.