Error logging is more general than just handling malformed rows. Essentially, any error related to an individual row can be recorded by error logging and the load can continue, except for the special case of UNIQUE/PRIMARY KEY violations. If there is such a violation, the loader will abort the load. Also, any error not related to an individual row (such as insufficient privileges) will abort the load operation.
Examples of the errors that can be caught by error logging include the following:
- NOT NULL violations
- Wrong number of columns
- Value format errors (for example, specifying "asdf" for an integer column)
- No matching child partition
- CHECK constraint violations
- Field length overflow (for example, specifying "asdf" for a varchar(2) column)
- Text/CSV format errors (for example, misplaced carriage return, unterminated quoted string, and so on)