【详述】
StarRocks版本：2.5和3.1
ADMIN SET FRONTEND CONFIG (“enable_pipeline_load” = “true”);
CREATE TABLE test.test_tb_pri (
user_id bigint(20) NOT NULL COMMENT “”,
name varchar(65533) NOT NULL COMMENT “”
) ENGINE=OLAP
PRIMARY KEY(user_id)
DISTRIBUTED BY HASH(user_id)
ORDER BY(user_id)
PROPERTIES (
“replication_num” = “3”,
“in_memory” = “false”,
“storage_format” = “DEFAULT”,
“enable_persistent_index” = “false”,
“compression” = “LZ4”
);
然后多次执行
truncate table test.test_tb_pri;
INSERT INTO test.test_tb_pri
select 1, ‘name_1’ union all
select 1, ‘name_2’ union all
select 1, ‘name_3’ union all
select 1, ‘name_4’ union all
select 1, ‘name_5’ union all
select 1, ‘name_6’ union all
select 1, ‘name_7’ union all
select 1, ‘name_8’ union all
select 1, ‘name_9’ union all
select 1, ‘name_10’ union all
select 1, ‘name_11’ union all
select 1, ‘name_12’ union all
select 1, ‘name_13’ union all
select 1, ‘name_14’;
select * from test_tb_pri;
MySQL [test]> select * from test_tb_pri;
±--------±--------+
| user_id | name |
±--------±--------+
| 1 | name_12 |
±--------±--------+
MySQL [test]> select * from test_tb_pri;
±--------±--------+
| user_id | name |
±--------±--------+
| 1 | name_8 |
±--------±--------+
enable_pipeline_load=true时，每次插入后查询的结果不一样,2.5和3.1都有这个问题，
然后把enable_pipeline_load改成false就没问题了；
3.2版本舍弃了enable_pipeline_load这个参数，请问3.2版本解决了插入不一致的问题了，如果解决了，怎么解决的，引入了什么机制？