Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Duplicate
-
5.5.1, 6.1.1
-
None
-
None
Description
Customer reported that after adding a new `null` column in columnstore and updading all 705 million rows and the message was "Rows matched: 0 Changed: 0 Warnings: 0" even though update was just fine.
MariaDB [dwhs]> select count(*) from sh_fact_impression_denorm;
|
+-----------+
|
| count(*) |
|
+-----------+
|
| 704371829 | |
+-----------+
|
1 row in set (0.508 sec) |
|
|
MariaDB [dwhs]> alter table sh_fact_impression_denorm add dms_publisher_key int; |
Query OK, 0 rows affected (14.655 sec) |
Records: 0 Duplicates: 0 Warnings: 0 |
|
|
MariaDB [dwhs]> update sh_fact_impression_denorm c, publisher1 s
|
-> set c.dms_publisher_key = s.dms_publisher_key
|
-> where c.affiliate_key = s.affiliate_key;
|
Query OK, 0 rows affected (12 min 57.315 sec) |
Rows matched: 0 Changed: 0 Warnings: 0 |
|
|
MariaDB [dwhs]> select count(*) from sh_fact_impression_denorm where dms_publisher_key is not null; |
+-----------+
|
| count(*) |
|
+-----------+
|
| 615313416 | |
+-----------+
|
1 row in set (0.537 sec) |
|
|
MariaDB [dwhs]> select count(*) from sh_fact_impression_denorm c, publisher1 s where c.affiliate_key = s.affiliate_key;
|
+-----------+
|
| count(*) |
|
+-----------+
|
| 701918781 | |
+-----------+
|
1 row in set (1.535 sec) |
So, the question is CS does not update null with a null once it determines the old value is also null?
Attachments
Issue Links
- relates to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-