expression: Support VALUES function for VectorFloat32

[EricZequan]

What problem does this PR solve?

Issue Number: ref #54245

Problem Summary:

What changed and how does it work?

Support VALUES().

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 47.82609% with 12 lines in your changes missing coverage. Please review.

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     #55151   +/-   ##
===========================================================================
  Coverage                                          ?   73.2647%           
===========================================================================
  Files                                             ?       1555           
  Lines                                             ?     432871           
  Branches                                          ?          0           
===========================================================================
  Hits                                              ?     317142           
  Misses                                            ?      94335           
  Partials                                          ?      21394           

Flag	Coverage Δ
integration	29.2665% <0.0000%> (?)
unit	71.7139% <47.8260%> (?)

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.4312% <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.

[breezewish]

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

Seems that this PR is still containing changes from other PRs?

There is still a huge difference between this PR and the reference PR.

The review cannot be done unless you make this PR atomic. Please fix it.

[EricZequan]

Seems that this PR is still containing changes from other PRs?

There is still a huge difference between this PR and the reference PR.

The review cannot be done unless you make this PR atomic. Please fix it.

It has been modified and the change should be clean.

[breezewish]

The rest LGTM. You did a good job!

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

/ok-to-test

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: breezewish, 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:

• pkg/expression/OWNERS [XuHuaiyu]

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-13 03:09:28.417762 +0000 UTC m=+237453.121231657: ☑️ agreed by breezewish.
• 2024-08-13 04:01:59.988255601 +0000 UTC m=+240604.691725244: ☑️ agreed by XuHuaiyu.

[breezewish]

/test unit-test

[EricZequan]

/retest