[BUG] unable to recover partition from recycle-bin when doing "insert overwrite"

[rohitrs1983]

Steps to reproduce the behavior (Required)

mysql> create table test_t1 ( id int(11), name varchar(128), da date ) engine=olap duplicate key(id) partition by range(da)( PARTITION p3 VALUES LESS THAN ('2023-01-01'), PARTITION p4 VALUES LESS THAN ('2024-01-01'), PARTITION p5 VALUES LESS THAN ('2025-01-01') ) distributed by hash(id) buckets 2 properties( "replication_num"="1" );

mysql> insert into test_t1 values(1, 'a', '2022-01-02');

mysql> insert into test_t1 values(2, 'a', '2023-01-02');

mysql> insert into test_t1 values(3, 'a', '2024-01-02');

mysql> select * from test_t1 order by id,name,da; +------+------+------------+ | id | name | da | +------+------+------------+ | 1 | a | 2022-01-02 | | 2 | a | 2023-01-02 | | 3 | a | 2024-01-02 | +------+------+------------+ 3 rows in set (0.04 sec)

mysql> insert overwrite test_t1 values(3, 'a', '2024-01-02');

mysql> select * from test_t1 order by id,name,da; +------+------+------------+ | id | name | da | +------+------+------------+ | 3 | a | 2024-01-02 | +------+------+------------+ 1 row in set (0.04 sec)

mysql> ALTER TABLE test_t1 DROP PARTITION p3 force; Query OK, 0 rows affected (0.01 sec)

mysql> ALTER TABLE test_t1 DROP PARTITION p4 force; Query OK, 0 rows affected (0.01 sec)

mysql> ALTER TABLE test_t1 DROP PARTITION p5 force; Query OK, 0 rows affected (0.01 sec)

mysql> recover partition p3 from test_t1; ERROR 1064 (HY000): No partition named 'p3' in recycle bin that belongs to table 'test_t1' mysql> recover partition p4 from test_t1; ERROR 1064 (HY000): No partition named 'p4' in recycle bin that belongs to table 'test_t1' mysql> recover partition p5 from test_t1;
ERROR 1064 (HY000): No partition named 'p5' in recycle bin that belongs to table 'test_t1' mysql>

Expected behavior (Required)

we should be able to recover the partion from recycle bin

Real behavior (Required)

StarRocks version (Required)

• starrocks-main

[kevincai]

@rohitrs1983 This should be the designed behavior when doing insert overwrite, the implicit partitions dropped due to insert overwrite is a force drop behavior.

@jaogoy Can you confirm the behavior?