Details
-
New Feature
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Done
Description
With FULL_NODUP mode, all columns are included in before image, but only updated columns are included in after image for UPDATE. While all columns are included in the after image for INSERT.
FULL_NODUP is for replacing FULL mode. It includes all data of the before and after image as FULL mode, but it uses less storage, especially in the case that only a few columns are updated.
This Jira is to track the contribution by Alibaba (https://github.com/MariaDB/server/pull/2803)
(Note that originally the MDEV was referring to the original Alibaba option, FULL_DIFFERENT. This was changed to FULL_NODUP to reflect the option implemented in MariaDB).
Attachments
Issue Links
- causes
-
MDEV-33049 Assertion `marked_for_write_or_computed()' failed in bool Field_new_decimal::store_value(const my_decimal*, int*)
-
- Closed
-
- relates to
-
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Andrei Elkin [ elkin ] |
| Assignee | Andrei Elkin [ elkin ] | Sergei Golubchik [ serg ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Assignee | Sergei Golubchik [ serg ] | Andrei Elkin [ elkin ] |
| Status | In Progress [ 3 ] | In Review [ 10002 ] |
| Priority | Major [ 3 ] | Critical [ 2 ] |
| Assignee | Andrei Elkin [ elkin ] | Andrew Hutchings [ JIRAUSER52179 ] |
| Status | In Review [ 10002 ] | Stalled [ 10000 ] |
| Fix Version/s | 11.4.1 [ 29523 ] | |
| Fix Version/s | 11.4 [ 29301 ] |
| Status | Stalled [ 10000 ] | In Testing [ 10301 ] |
| Assignee | Andrew Hutchings [ JIRAUSER52179 ] | Elena Stepanova [ elenst ] |
| Fix Version/s | 11.4 [ 29301 ] | |
| Fix Version/s | 11.4.1 [ 29523 ] |
| Component/s | Replication [ 10100 ] | |
| Assignee | Elena Stepanova [ elenst ] | Roel Van de Paar [ roel ] |
| Link |
This issue relates to |
| Issue Type | Task [ 3 ] | New Feature [ 2 ] |
| Summary | Add FULL_DIFFERENT mode for binlog_row_image | FULL_NODUP mode for binlog_row_image |
| Link |
This issue causes |
| Assignee | Roel Van de Paar [ roel ] | Ramesh Sivaraman [ JIRAUSER48189 ] |
| Link | This issue causes TODO-4495 [ TODO-4495 ] |
| Link | This issue causes TODO-4495 [ TODO-4495 ] |
| Link | This issue is part of TODO-4495 [ TODO-4495 ] |
| Labels | Preview_11.4 |
| Assignee | Ramesh Sivaraman [ JIRAUSER48189 ] | Andrew Hutchings [ JIRAUSER52179 ] |
| Status | In Testing [ 10301 ] | Stalled [ 10000 ] |
| Fix Version/s | 11.4.1 [ 29523 ] | |
| Fix Version/s | 11.4 [ 29301 ] | |
| Resolution | Done [ 10200 ] | |
| Status | Stalled [ 10000 ] | Closed [ 6 ] |
| Description |
With FULL_DIFFERENT mode, all columns are included in before image, but only updated columns are included in after image for UPDATE. While all columns are included in the after image for INSERT.
FULL_DIFFERENT is for replacing FULL mode. It includes all data of the before and after image as FULL mode, but it uses less storage, especially in the case that only a few columns are updated. This Jira is to track the contribution by Alibaba (https://github.com/MariaDB/server/pull/2803) |
With FULL_NODUP mode, all columns are included in before image, but only updated columns are included in after image for UPDATE. While all columns are included in the after image for INSERT.
FULL_NODUP is for replacing FULL mode. It includes all data of the before and after image as FULL mode, but it uses less storage, especially in the case that only a few columns are updated. This Jira is to track the contribution by Alibaba (https://github.com/MariaDB/server/pull/2803) (Note that originally the MDEV was referring to the original Alibaba option, FULL_DIFFERENT. This was changed to FULL_NODUP to reflect the option implemented in MariaDB). |
| Remote Link | This issue links to "Page (MariaDB Confluence)" [ 36727 ] |
| Remote Link | This issue links to "Page (MariaDB Confluence)" [ 36727 ] |