Details
-
New Feature
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
23.02.10, 23.02.15, 23.10.4
-
None
-
2025-9
Description
Summary:
Customers run automation every hour or day sometimes looking to drop data after x number of days. They do so by running calshowpartitions on everytable and running caldroppartitions because the system is large. However their automation hits weird errors when they run into the following cases that claim year 32767. Empty paritions will be initialized with "random" values, even after a select like should be initialized with 0 values or at least N/A.
Reproduction:
create table t5 ( d date) engine=columnstore;
|
SELECT calShowPartitions('t5','d'); |
select min(d) from t5;
|
SELECT calShowPartitions('t5','d'); |
Actual Outcome:
--------------------------------------------------------------------------------------------------------------------------------------------------------------+
|
| Part# Min Max Status
|
0.0.3 32767-15-63 32768-00-00 Enabled | |
Expected Outcome:
or 0 as string dataypes already show N/A. this way we separate data exists vs no data exists for calShowPartitions output
MariaDB [test]> SELECT calShowPartitions('t5','d'); |
+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
|
| calShowPartitions('t5','d') | |
+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
|
| Part# Min Max Status
|
0.0.1 N/A N/A Enabled | |
+--------------------------------------------------------------------------------------------------------------------------------------------------------------+
|
1 row in set (0.052 sec) |
|
