diff options
author | Sergei Petrunia <psergey@askmonty.org> | 2021-12-02 11:54:10 +0300 |
---|---|---|
committer | Sergei Petrunia <psergey@askmonty.org> | 2022-01-19 18:10:11 +0300 |
commit | 1d14176ec4e74fcae165bf9633f2763805d9768a (patch) | |
tree | 81bd0c7be6e0798bac2a3edf9f79cdc58a84aa4d /mysql-test/main/statistics_json.test | |
parent | be55ad0d34e27a67b85fa8fa21ccb9384bf31a64 (diff) | |
download | mariadb-git-1d14176ec4e74fcae165bf9633f2763805d9768a.tar.gz |
MDEV-26519: Improved histograms: Make JSON parser efficient
Previous JSON parser was using an API which made the parsing
inefficient: the same JSON contents was parsed again and again.
Switch to using a lower-level parsing API which allows to do
parsing in an efficient way.
Diffstat (limited to 'mysql-test/main/statistics_json.test')
-rw-r--r-- | mysql-test/main/statistics_json.test | 9 |
1 files changed, 0 insertions, 9 deletions
diff --git a/mysql-test/main/statistics_json.test b/mysql-test/main/statistics_json.test index 23e5e7395a7..b0a1795c235 100644 --- a/mysql-test/main/statistics_json.test +++ b/mysql-test/main/statistics_json.test @@ -46,62 +46,53 @@ drop table ten; UPDATE mysql.column_stats SET histogram='["not-what-you-expect"]' WHERE table_name='t1_json'; FLUSH TABLES; ---error ER_JSON_HISTOGRAM_PARSE_FAILED explain select * from t1_json limit 1; UPDATE mysql.column_stats SET histogram='{"histogram_hb_v2":"not-histogram"}' WHERE table_name='t1_json'; FLUSH TABLES; ---error ER_JSON_HISTOGRAM_PARSE_FAILED explain select * from t1_json limit 1; UPDATE mysql.column_stats SET histogram='{"histogram_hb_v2":["not-a-bucket"]}' WHERE table_name='t1_json'; FLUSH TABLES; ---error ER_JSON_HISTOGRAM_PARSE_FAILED explain select * from t1_json limit 1; UPDATE mysql.column_stats SET histogram='{"histogram_hb_v2":[{"no-expected-members":1}]}' WHERE table_name='t1_json'; FLUSH TABLES; ---error ER_JSON_HISTOGRAM_PARSE_FAILED explain select * from t1_json limit 1; UPDATE mysql.column_stats SET histogram='{"histogram_hb_v2":[{"start":{}}]}' WHERE table_name='t1_json'; FLUSH TABLES; ---error ER_JSON_HISTOGRAM_PARSE_FAILED explain select * from t1_json limit 1; UPDATE mysql.column_stats SET histogram='{"histogram_hb_v2":[{"start":"aaa", "size":"not-an-integer"}]}' WHERE table_name='t1_json'; FLUSH TABLES; ---error ER_JSON_HISTOGRAM_PARSE_FAILED explain select * from t1_json limit 1; UPDATE mysql.column_stats SET histogram='{"histogram_hb_v2":[{"start":"aaa", "size":0.25}]}' WHERE table_name='t1_json'; FLUSH TABLES; ---error ER_JSON_HISTOGRAM_PARSE_FAILED explain select * from t1_json limit 1; UPDATE mysql.column_stats SET histogram='{"histogram_hb_v2":[{"start":"aaa", "size":0.25, "ndv":1}]}' WHERE table_name='t1_json'; FLUSH TABLES; ---error ER_JSON_HISTOGRAM_PARSE_FAILED explain select * from t1_json limit 1; UPDATE mysql.column_stats SET histogram='{"histogram_hb_v2":[]}' WHERE table_name='t1_json'; FLUSH TABLES; ---error ER_JSON_HISTOGRAM_PARSE_FAILED explain select * from t1_json limit 1; --source include/have_sequence.inc |