In the Fusioninsight HD system, if dirty data is generated during the running of the Loader job, the status of the Loader job execution result must be failure.

Question

Options

• ATrue
• BFalse

• A
  20% (4)
• B
  80% (16)

Explanation

B is correct because FusionInsight HD's Loader is designed to handle dirty data gracefully - when a job encounters records that fail validation or transformation rules, those records can be logged or skipped according to the job's configuration, while the rest of the data continues processing successfully. The job can complete with a partial success or success with warnings status rather than an outright failure.

Why A is wrong: Assuming dirty data always causes failure conflates data quality issues with job execution failures. A Loader job fails when it cannot execute its core logic (e.g., connectivity loss, schema mismatch, insufficient permissions), not simply because some records are malformed. Dirty data tolerance is a configurable behavior, not a hard stop.

Memory tip: Think of Loader like a postal sorter - if a few packages have bad addresses, the sorter doesn't shut down the whole facility; it sets those aside and keeps processing the rest. Job failure means the machine broke, not that some packages were undeliverable.

No community discussion yet for this question.