…f newly inserted rows in partial update (#41232)

Currently, Doris use strict mode to decide if newly inserted rows should
be appended or report an error in partial update, which is hard to use.
This PR add a new session variable and load property
`partial_update_new_key_behavior` to control the behavior of newly
inserted rows in partial update.
`partial_update_new_key_behavior` has ~three~ two options:
- `APPEND`: append the newly inserted rows
- ~`IGNORE`: delete the newly inserted rows silently(will not be taken
into filtered rows)~
- `ERROR`: report error if meet newly inserted rows, and the error msg
will contains one row's keys which is not in table.

---
The reason for not supporting `IGNORE` mode: To support `IGNORE` mode,
we need to add delete sign for newly inserted rows in partial update to
delete them rather than use delete bitmap mark to delete them because
compaction will not use delete bitmap when reading data. Also, we need
to record the rows whose delete sign is added by us in this situation
for resolving conflicts in publish phase to avoid wrongly delete the
rows if there are another concurrent load insert some of these rows
successfully. This increases code complexity and is error-prone.

Doc: apache/doris-website#2472

…f newly inserted rows in partial update (apache#41232)

Currently, Doris use strict mode to decide if newly inserted rows should
be appended or report an error in partial update, which is hard to use.
This PR add a new session variable and load property
`partial_update_new_key_behavior` to control the behavior of newly
inserted rows in partial update.
`partial_update_new_key_behavior` has ~three~ two options:
- `APPEND`: append the newly inserted rows
- ~`IGNORE`: delete the newly inserted rows silently(will not be taken
into filtered rows)~
- `ERROR`: report error if meet newly inserted rows, and the error msg
will contains one row's keys which is not in table.

---
The reason for not supporting `IGNORE` mode: To support `IGNORE` mode,
we need to add delete sign for newly inserted rows in partial update to
delete them rather than use delete bitmap mark to delete them because
compaction will not use delete bitmap when reading data. Also, we need
to record the rows whose delete sign is added by us in this situation
for resolving conflicts in publish phase to avoid wrongly delete the
rows if there are another concurrent load insert some of these rows
successfully. This increases code complexity and is error-prone.

Doc: apache/doris-website#2472

…f newly inserted rows in partial update (apache#41232)

Currently, Doris use strict mode to decide if newly inserted rows should
be appended or report an error in partial update, which is hard to use.
This PR add a new session variable and load property
`partial_update_new_key_behavior` to control the behavior of newly
inserted rows in partial update.
`partial_update_new_key_behavior` has ~three~ two options:
- `APPEND`: append the newly inserted rows
- ~`IGNORE`: delete the newly inserted rows silently(will not be taken
into filtered rows)~
- `ERROR`: report error if meet newly inserted rows, and the error msg
will contains one row's keys which is not in table.

---
The reason for not supporting `IGNORE` mode: To support `IGNORE` mode,
we need to add delete sign for newly inserted rows in partial update to
delete them rather than use delete bitmap mark to delete them because
compaction will not use delete bitmap when reading data. Also, we need
to record the rows whose delete sign is added by us in this situation
for resolving conflicts in publish phase to avoid wrongly delete the
rows if there are another concurrent load insert some of these rows
successfully. This increases code complexity and is error-prone.

Doc: apache/doris-website#2472

…f newly inserted rows in partial update (apache#41232)

Currently, Doris use strict mode to decide if newly inserted rows should
be appended or report an error in partial update, which is hard to use.
This PR add a new session variable and load property
`partial_update_new_key_behavior` to control the behavior of newly
inserted rows in partial update.
`partial_update_new_key_behavior` has ~three~ two options:
- `APPEND`: append the newly inserted rows
- ~`IGNORE`: delete the newly inserted rows silently(will not be taken
into filtered rows)~
- `ERROR`: report error if meet newly inserted rows, and the error msg
will contains one row's keys which is not in table.

---
The reason for not supporting `IGNORE` mode: To support `IGNORE` mode,
we need to add delete sign for newly inserted rows in partial update to
delete them rather than use delete bitmap mark to delete them because
compaction will not use delete bitmap when reading data. Also, we need
to record the rows whose delete sign is added by us in this situation
for resolving conflicts in publish phase to avoid wrongly delete the
rows if there are another concurrent load insert some of these rows
successfully. This increases code complexity and is error-prone.

Doc: apache/doris-website#2472

…f newly inserted rows in partial update (apache#41232)

Currently, Doris use strict mode to decide if newly inserted rows should
be appended or report an error in partial update, which is hard to use.
This PR add a new session variable and load property
`partial_update_new_key_behavior` to control the behavior of newly
inserted rows in partial update.
`partial_update_new_key_behavior` has ~three~ two options:
- `APPEND`: append the newly inserted rows
- ~`IGNORE`: delete the newly inserted rows silently(will not be taken
into filtered rows)~
- `ERROR`: report error if meet newly inserted rows, and the error msg
will contains one row's keys which is not in table.

---
The reason for not supporting `IGNORE` mode: To support `IGNORE` mode,
we need to add delete sign for newly inserted rows in partial update to
delete them rather than use delete bitmap mark to delete them because
compaction will not use delete bitmap when reading data. Also, we need
to record the rows whose delete sign is added by us in this situation
for resolving conflicts in publish phase to avoid wrongly delete the
rows if there are another concurrent load insert some of these rows
successfully. This increases code complexity and is error-prone.

Doc: apache/doris-website#2472

…f newly inserted rows in partial update (apache#41232)

Currently, Doris use strict mode to decide if newly inserted rows should
be appended or report an error in partial update, which is hard to use.
This PR add a new session variable and load property
`partial_update_new_key_behavior` to control the behavior of newly
inserted rows in partial update.
`partial_update_new_key_behavior` has ~three~ two options:
- `APPEND`: append the newly inserted rows
- ~`IGNORE`: delete the newly inserted rows silently(will not be taken
into filtered rows)~
- `ERROR`: report error if meet newly inserted rows, and the error msg
will contains one row's keys which is not in table.

---
The reason for not supporting `IGNORE` mode: To support `IGNORE` mode,
we need to add delete sign for newly inserted rows in partial update to
delete them rather than use delete bitmap mark to delete them because
compaction will not use delete bitmap when reading data. Also, we need
to record the rows whose delete sign is added by us in this situation
for resolving conflicts in publish phase to avoid wrongly delete the
rows if there are another concurrent load insert some of these rows
successfully. This increases code complexity and is error-prone.

Doc: apache/doris-website#2472

…f newly inserted rows in partial update (apache#41232)

Currently, Doris use strict mode to decide if newly inserted rows should
be appended or report an error in partial update, which is hard to use.
This PR add a new session variable and load property
`partial_update_new_key_behavior` to control the behavior of newly
inserted rows in partial update.
`partial_update_new_key_behavior` has ~three~ two options:
- `APPEND`: append the newly inserted rows
- ~`IGNORE`: delete the newly inserted rows silently(will not be taken
into filtered rows)~
- `ERROR`: report error if meet newly inserted rows, and the error msg
will contains one row's keys which is not in table.

---
The reason for not supporting `IGNORE` mode: To support `IGNORE` mode,
we need to add delete sign for newly inserted rows in partial update to
delete them rather than use delete bitmap mark to delete them because
compaction will not use delete bitmap when reading data. Also, we need
to record the rows whose delete sign is added by us in this situation
for resolving conflicts in publish phase to avoid wrongly delete the
rows if there are another concurrent load insert some of these rows
successfully. This increases code complexity and is error-prone.

Doc: apache/doris-website#2472

…f newly inserted rows in partial update (apache#41232)

Currently, Doris use strict mode to decide if newly inserted rows should
be appended or report an error in partial update, which is hard to use.
This PR add a new session variable and load property
`partial_update_new_key_behavior` to control the behavior of newly
inserted rows in partial update.
`partial_update_new_key_behavior` has ~three~ two options:
- `APPEND`: append the newly inserted rows
- ~`IGNORE`: delete the newly inserted rows silently(will not be taken
into filtered rows)~
- `ERROR`: report error if meet newly inserted rows, and the error msg
will contains one row's keys which is not in table.

---
The reason for not supporting `IGNORE` mode: To support `IGNORE` mode,
we need to add delete sign for newly inserted rows in partial update to
delete them rather than use delete bitmap mark to delete them because
compaction will not use delete bitmap when reading data. Also, we need
to record the rows whose delete sign is added by us in this situation
for resolving conflicts in publish phase to avoid wrongly delete the
rows if there are another concurrent load insert some of these rows
successfully. This increases code complexity and is error-prone.

Doc: apache/doris-website#2472