server: Return VECTOR as LONGTEXT for clients

[EricZequan]

What problem does this PR solve?

Issue Number: ref #54245

Problem Summary:

What changed and how does it work?

Some clients will throw errors when meeting unknown field types, like go-sql-driver/mysql. This PR makes VECTOR type return as LONGTEXT to maximize compatibility.

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

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

Additional details and impacted files

@@                             Coverage Diff                             @@
##             feature/vector-search/vector-data-type     #55223   +/-   ##
===========================================================================
  Coverage                                          ?   74.7825%           
===========================================================================
  Files                                             ?       1561           
  Lines                                             ?     440263           
  Branches                                          ?          0           
===========================================================================
  Hits                                              ?     329240           
  Misses                                            ?      90791           
  Partials                                          ?      20232           

Flag	Coverage Δ
integration	49.5134% <40.0000%> (?)
unit	71.8079% <100.0000%> (?)

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

[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.

[hawkingrei]

/retest

[EricZequan]

/test idc-jenkins-ci-tidb/check_dev_2

[ti-chi-bot]

@EricZequan: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test build
• /test check-dev
• /test check-dev2
• /test mysql-test
• /test pull-br-integration-test
• /test pull-integration-ddl-test
• /test pull-lightning-integration-test
• /test pull-mysql-client-test
• /test unit-test

The following commands are available to trigger optional jobs:

• /test pingcap/tidb/canary_ghpr_unit_test
• /test pull-common-test
• /test pull-e2e-test
• /test pull-integration-common-test
• /test pull-integration-copr-test
• /test pull-integration-jdbc-test
• /test pull-integration-mysql-test
• /test pull-integration-nodejs-test
• /test pull-sqllogic-test
• /test pull-tiflash-test

Use /test all to run the following jobs that were automatically triggered:

• pingcap/tidb/ghpr_build
• pingcap/tidb/ghpr_check
• pingcap/tidb/ghpr_check2
• pingcap/tidb/ghpr_mysql_test
• pingcap/tidb/ghpr_unit_test
• pingcap/tidb/pull_integration_ddl_test
• pingcap/tidb/pull_mysql_client_test

In response to this:

/test idc-jenkins-ci-tidb/check_dev_2

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/test-infra repository.

[tiprow]

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

In response to this:

/test idc-jenkins-ci-tidb/check_dev_2

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.

[breezewish]

Can you rebase this PR and exclude changes of #55134 and #55151? 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.

[breezewish]

Good!

[breezewish]

/ok-to-test

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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 [breezewish,tangenta]

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

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-08-12 13:44:55.557720862 +0000 UTC m=+189180.261190505: ☑️ agreed by breezewish.
• 2024-08-20 04:36:17.394689268 +0000 UTC m=+240172.529139390: ☑️ agreed by tangenta.

[EricZequan]

/retest