Partitioning changes the query result after EXCHANGE PARTITION with a table that has a VECTOR INDEX

--source include/have_partition.inc

--source include/have_innodb.inc

--let $v= query_get_value(SELECT COUNT(*) AS c FROM information_schema.GLOBAL_VARIABLES WHERE VARIABLE_NAME='MHNSW_MAX_CACHE_SIZE', c, 1)

if (!$v)

{

  --skip Needs the VECTOR data type

}

CREATE TABLE t1 (a INT, v VECTOR(2) NOT NULL) ENGINE=InnoDB PARTITION BY RANGE (a) (PARTITION p0 VALUES LESS THAN (10), PARTITION p1 VALUES LESS THAN (20));

INSERT INTO t1 VALUES (1, VEC_FromText('[100,100]')),(2, VEC_FromText('[200,200]')),(3, VEC_FromText('[300,300]'));

CREATE TABLE t2 (a INT, v VECTOR(2) NOT NULL, VECTOR INDEX (v)) ENGINE=InnoDB;

INSERT INTO t2 VALUES (5, VEC_FromText('[1,2]')),(6, VEC_FromText('[3,4]'));

# t1 has no VECTOR INDEX and t2 has one, so the definitions differ

--error 0,ER_TABLES_DIFFERENT_METADATA

ALTER TABLE t1 EXCHANGE PARTITION p0 WITH TABLE t2;

if (!$mysql_errno)

{

  SELECT COUNT(*) INTO @c FROM (SELECT a FROM t2 ORDER BY VEC_DISTANCE_EUCLIDEAN(v, VEC_FromText('[1,2]')) LIMIT 3) AS d;

  --let $c= query_get_value(SELECT @c AS c, c, 1)

  if ($c != 3)

  {

    --die The vector search on t2 finds $c of its 3 rows after EXCHANGE PARTITION, which ignored its VECTOR INDEX

  }

}

DROP TABLE t1, t2;

mysqltest: At line 22: The vector search on t2 finds 2 of its 3 rows after EXCHANGE PARTITION, which ignored its VECTOR INDEX