Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

merge main #131

Merged
merged 24 commits into from
Jun 4, 2024
Merged

merge main #131

merged 24 commits into from
Jun 4, 2024

Conversation

jiangxinmeng1
Copy link

What type of PR is this?

  • API-change
  • BUG
  • Improvement
  • Documentation
  • Feature
  • Test and CI
  • Code Refactoring

Which issue(s) this PR fixes:

issue #

What this PR does / why we need it:

LeftHandCold and others added 24 commits June 3, 2024 02:27
Each tenant of the current mo has a mo_snapshot table to store snapshot information. GC needs to consume all mo_snapshot tables.

Approved by: @XuPeng-SH
…xorigin#16558)

1. filter CNs that are not in working state.
2. add some logs for migration

Approved by: @zhangxu19830126
To avoid List() operations on oss, tke or s3, you need to add the Cost interface.

Approved by: @reusee, @XuPeng-SH
aim to exclude the `system,system_metrics` part case.
changes:
1. move `cases/table/system_table_cases` system,system_metrics part into individule case file.

Approved by: @heni02
Remove some unnecessary MustStrCol, MustBytesCol calls.

Approved by: @daviszhen, @reusee, @m-schen, @aunjgr, @XuPeng-SH
…16600)

fix a bug that cause load performance regression issue

Approved by: @m-schen
add case for restore pub_sub

Approved by: @heni02
…trixorigin#16366)

During `KNN Select` and `Mapping Entries to Centroids via CROSS_JOIN_L2`, we can make use of L2DistanceSq instead of L2Distance, as it avoids `Sqrt()`. We can see the improvement in QPS for SIFT128 from 90 to 100. However, for GIST960, the QPS did not change much.

L2DistanceSq is suitable only when there is a comparison (ie ORDER BY), and when the absolute value (ie actual L2Distance) is not required.
- In the case of `CROSS JOIN L2` we find the nearest centroid for the Entry using `L2DistanceSq`. `CROSS JOIN L2` is used in both INSERT and CREATE INDEX.
- In the case of `KNN SELECT`, our query has ORDER BY L2_DISTANCE(...), which can make use of `L2DistanceSq` as the L2Distance value is not explicitly required.

**NOTE:** L2DistanceSq is not suitable in Kmenas++ for Centroid Computation, as it will impact the centroids picked.

Approved by: @heni02, @m-schen, @aunjgr, @badboynt1
add sharding metrics

Approved by: @aptend
fix data race

Approved by: @reusee
Reshape objects block by block.

Approved by: @XuPeng-SH
…16551)

- system variable now is account isolated
- table `mo_mysql_compatibility_mode` only saves delta info between account's and cluster's default system variable values
- always use session variable except `show global variables`

Approved by: @daviszhen, @aunjgr, @aressu1985
When truncate table, if the table does not have any auto-incr col, there is no need to call the Reset interface of increment_service

Approved by: @ouyuanning
…gin#16604)

1. bump go version from 1.21.5 to 1.22.3
2. fix `make compose` to make it work
3. `make ut` will read `UT_WORKDIR` env variable to store report, it will be `$HOME` if `UT_WORKDIR` is empty

Approved by: @zhangxu19830126, @sukki37
remove isMerge from build operator

Approved by: @m-schen
@XuPeng-SH XuPeng-SH merged commit 37e4d9a into XuPeng-SH:TombstoneBasedMO Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.