[BugFix] Fix duplicated error rows in load tracking log

[wyb]

Why I'm doing:

CREATE TABLE `t3` (
  `k1` bigint NOT NULL,
  `k2` bigint NOT NULL,
  `k3` bigint NOT NULL
)

insert into t3 values (null, null, null);

mysql> select tracking_log from information_schema.load_tracking_logs where job_id=284223;
+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| tracking_log                                                                                                                                                                                                 |
+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Error: NULL value in non-nullable column 'k1'. Row: [NULL, NULL, NULL]
Error: NULL value in non-nullable column 'k2'. Row: [0, NULL, NULL]
Error: NULL value in non-nullable column 'k3'. Row: [0, 0, NULL]
 |
+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.05 sec)

there are 3 rows in tracking logs and the last 2 rows are wrong.

What I'm doing:

mysql> select tracking_log from information_schema.load_tracking_logs where job_id=284327;
+-------------------------------------------------------------------------+
| tracking_log                                                            |
+-------------------------------------------------------------------------+
| Error: NULL value in non-nullable column 'k1'. Row: [NULL, NULL, NULL]
 |
+-------------------------------------------------------------------------+
1 row in set (0.02 sec)

only record the first invalid column k1 for the inserted row.

Fixes #issue

What type of PR is this:

• BugFix
• Feature
• Enhancement
• Refactor
• UT
• Doc
• Tool

Does this PR entail a change in behavior?

• Yes, this PR will result in a change in behavior.
• No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

• Interface/UI changes: syntax, type conversion, expression evaluation, display information
• Parameter changes: default values, similar parameters but with different default values
• Policy changes: use new policy to replace old one, functionality automatically enabled
• Feature removed
• Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

• I have added test cases for my bug fix or my new feature
• This pr needs user documentation (for new or modified features or behaviors)
  • I have added documentation for my new feature or new function
• This is a backport pr

Bugfix cherry-pick branch check:

• I have checked the version labels which the pr will be auto-backported to the target branch
  • 3.3
  • 3.2
  • 3.1
  • 3.0
  • 2.5

[github-actions]

[FE Incremental Coverage Report]

✅ pass : 0 / 0 (0%)

[github-actions]

[BE Incremental Coverage Report]

✅ pass : 1 / 1 (100.00%)

file detail

	path	covered_line	new_line	coverage	not_covered_line_detail
🔵	be/src/exec/tablet_sink.cpp	1	1	100.00%	[]

[github-actions]

@Mergifyio backport branch-3.3

[github-actions]

@Mergifyio backport branch-3.2

[github-actions]

@Mergifyio backport branch-3.1

[mergify]

backport branch-3.3

✅ Backports have been created

• #45718 [BugFix] Fix duplicated error rows in load tracking log (backport #45500) has been created for branch branch-3.3

[mergify]

backport branch-3.2

✅ Backports have been created

• #45719 [BugFix] Fix duplicated error rows in load tracking log (backport #45500) has been created for branch branch-3.2

[mergify]

backport branch-3.1

✅ Backports have been created

• #45720 [BugFix] Fix duplicated error rows in load tracking log (backport #45500) has been created for branch branch-3.1