*: support fixed dimension vector

[EricZequan]

What problem does this PR solve?

Issue Number: ref #54245

Problem Summary:

What changed and how does it work?

Support fixed size vector types like VECTOR(3).

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)

mysql> DROP TABLE t;
Query OK, 0 rows affected (0.12 sec)

mysql> create table t(embedding VECTOR);
Query OK, 0 rows affected (0.06 sec)

mysql> INSERT INTO t VALUES ('[1,2,3]'), ('[4,5]'), ('[6]');
Query OK, 3 rows affected (0.01 sec)
Records: 3  Duplicates: 0  Warnings: 0

mysql> ALTER TABLE t MODIFY COLUMN embedding VECTOR(0);
ERROR 1105 (HY000): vector has 3 dimensions, does not fit VECTOR(0)
mysql> ALTER TABLE t MODIFY COLUMN embedding VECTOR(16001);
ERROR 1105 (HY000): vector cannot have more than 16000 dimensions
mysql> ALTER TABLE t MODIFY COLUMN embedding VECTOR(3);
ERROR 1105 (HY000): vector has 2 dimensions, does not fit VECTOR(3)
mysql> DELETE FROM t WHERE VEC_DIMS(embedding) != 3;
Query OK, 2 rows affected (0.01 sec)

mysql> ALTER TABLE t MODIFY COLUMN embedding VECTOR(3);
Query OK, 0 rows affected (0.14 sec)

mysql> SHOW COLUMNS FROM t;
+-----------+------------------+------+------+---------+-------+
| Field     | Type             | Null | Key  | Default | Extra |
+-----------+------------------+------+------+---------+-------+
| embedding | vector<float>(3) | YES  |      | NULL    |       |
+-----------+------------------+------+------+---------+-------+
1 row in set (0.00 sec)

mysql> ALTER TABLE t MODIFY COLUMN embedding VECTOR;
Query OK, 0 rows affected (0.07 sec)

mysql> 
mysql> SHOW COLUMNS FROM t;
+-----------+---------------+------+------+---------+-------+
| Field     | Type          | Null | Key  | Default | Extra |
+-----------+---------------+------+------+---------+-------+
| embedding | vector<float> | YES  |      | NULL    |       |
+-----------+---------------+------+------+---------+-------+
1 row in set (0.00 sec)

• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[tiprow]

Hi @EricZequan. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[EricZequan]

/retest

[tiprow]

@EricZequan: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[codecov]

Codecov Report

Attention: Patch coverage is 72.13115% with 17 lines in your changes missing coverage. Please review.

Please upload report for BASE (feature/vector-search/vector-data-type@5389de9). Learn more about missing BASE report.

Additional details and impacted files

@@                             Coverage Diff                             @@
##             feature/vector-search/vector-data-type     #55002   +/-   ##
===========================================================================
  Coverage                                          ?   75.4096%           
===========================================================================
  Files                                             ?       1561           
  Lines                                             ?     439477           
  Branches                                          ?          0           
===========================================================================
  Hits                                              ?     331408           
  Misses                                            ?      87508           
  Partials                                          ?      20561           

Flag	Coverage Δ
integration	50.8258% <0.0000%> (?)
unit	71.6977% <72.1311%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	52.9656% <0.0000%> (?)
parser	∅ <0.0000%> (?)
br	63.1957% <0.0000%> (?)

[breezewish]

This part is missing?

[JaySon-Huang]

the maximum dimension supported in MySQL is 16383. We should align to it according to the feature spec. /cc @breezewish

[breezewish]

Nice catch. Please also add a TiDB-CSE PR to update this limit. @EricZequan

[EricZequan]

Roger that.🫡

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-08-05 07:37:47.886995853 +0000 UTC m=+251197.754094939: ☑️ agreed by breezewish.
• 2024-08-05 08:46:43.746153468 +0000 UTC m=+255333.613252557: ☑️ agreed by tangenta.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: breezewish, hawkingrei, tangenta, XuHuaiyu

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [XuHuaiyu,breezewish,hawkingrei,tangenta]
• pkg/ddl/OWNERS [tangenta]
• pkg/expression/OWNERS [XuHuaiyu]
• pkg/planner/OWNERS [hawkingrei]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment