copr: Support VECTOR for RowFormatv1

[EricZequan]

What problem does this PR solve?

Issue Number: ref #54245

Problem Summary:

What changed and how does it work?

When CSV data is loaded via LOAD DATA statement, it turns out that row is encoded using Format v1:

LOAD DATA LOCAL INFILE '/Users/breezewish/Downloads/backup_llama_index_rag_test/test.llama_index_rag_test.0000000010000.csv' INTO TABLE `llama_index_rag_test` FIELDS TERMINATED BY ',' ENCLOSED BY '"' LINES TERMINATED BY '\r\n' IGNORE 1 LINES;

And it causes problems:

mysql> select * from llama_index_rag_test limit 10;
ERROR 1105 (HY000): invalid data type: unsupported data type `20`

This PR make it work.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• 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 78.26087% with 5 lines in your changes missing coverage. Please review.

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

Additional details and impacted files

@@                             Coverage Diff                             @@
##             feature/vector-search/vector-data-type     #55149   +/-   ##
===========================================================================
  Coverage                                          ?   73.3487%           
===========================================================================
  Files                                             ?       1561           
  Lines                                             ?     440051           
  Branches                                          ?          0           
===========================================================================
  Hits                                              ?     322772           
  Misses                                            ?      97305           
  Partials                                          ?      19974           

Flag	Coverage Δ
integration	20.5019% <0.0000%> (?)
unit	71.7118% <78.2608%> (?)

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	46.1682% <0.0000%> (?)

[breezewish]

Can you rebase this PR and exclude changes of #55134? I think these PRs can be reviewed concurrently.

If you cannot make this PR atomic, i.e. only includes the changes of what it describes, then it cannot be reviewed.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:

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

Needs approval from an approver in each of these files:

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