Default value population for new fields in rotated/extended tables may cause poorly performing UNION queries - Known Error

Default value population for new fields in rotated/extended tables may cause poorly performing UNION queries Description Default value population for new fields in rotated or extended tables do not target specific table shards. This generates poorly performing UNION queries to acquire the datasets to update.

Steps to Reproduce

1. Activate SQL debugging. 2. Add a new field with a default value to a rotated/extended table. 3. Observe the queries to get the sys_id chunks. These are UNIONing all tables (e.g. sys_email0000, sys_email0001) instead of using only the required shard one at the time.

Workaround This problem is under review and targeted to be fixed in a future release. To receive notifications when more information becomes available, subscribe to this Known Error article by clicking the Subscribe button at the top right of this form.