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

[Bug]: table with fulltext index ,delete from table where xxx failed #20149

Open
1 task done
tom-csf opened this issue Nov 18, 2024 · 8 comments · Fixed by #20230
Open
1 task done

[Bug]: table with fulltext index ,delete from table where xxx failed #20149

tom-csf opened this issue Nov 18, 2024 · 8 comments · Fixed by #20230
Assignees
Labels
phase/testing severity/s0 Extreme impact: Cause the application to break down and seriously affect the use
Milestone

Comments

@tom-csf
Copy link

tom-csf commented Nov 18, 2024

Is there an existing issue for the same bug?

  • I have checked the existing issues.

Branch Name

2.0-dev

Commit ID

b574c10

Other Environment Information

- Hardware parameters:
- OS type:
- Others:

Actual Behavior

image

Expected Behavior

No response

Steps to Reproduce

load tpch 1g data to tpch_1g database
create table nation3 like nation;
insert into nation3 select * from nation;
set experimental_fulltext_index=1;
create fulltext index fdx9 on nation3(N_COMMENT);
delete from nation3 where n_nationkey = 10;

Additional information

https://shanghai.idc.matrixorigin.cn:30001/explore?panes=%7B%22O2c%22:%7B%22datasource%22:%22loki%22,%22queries%22:%5B%7B%22refId%22:%22A%22,%22expr%22:%22%7Bnamespace%3D%5C%22mo-chaos-b574c10-202411181405%5C%22%7D%20%7C%3D%20%60anic%20this%20error%20should%20not%20be%20logged%60%22,%22queryType%22:%22range%22,%22datasource%22:%7B%22type%22:%22loki%22,%22uid%22:%22loki%22%7D,%22editorMode%22:%22builder%22%7D%5D,%22range%22:%7B%22from%22:%221731919813000%22,%22to%22:%221731919933000%22%7D%7D%7D&schemaVersion=1&orgId=1

@tom-csf tom-csf added this to the 2.0.1 milestone Nov 18, 2024
@cpegeric
Copy link
Contributor

image

@jiangxinmeng1
Copy link
Contributor

jiangxinmeng1 commented Nov 19, 2024

The type of primary key vector in delete batch doesn't match the index table. The primary key is bigint unsign, while the pk in delete batch is int
企业微信截图_17319834958753

the Table Scan result is correct, primary key is bigint unsign
屏幕截图 2024-11-19 150015

It looks like the primary key of original table. The type and value is the same as the original pk.
image

@XuPeng-SH XuPeng-SH assigned cpegeric and unassigned XuPeng-SH Nov 19, 2024
@XuPeng-SH
Copy link
Contributor

@cpegeric It looks like the pk type used for the secondary index table deletion is incorrectly using the pk type of the original table.

@cpegeric
Copy link
Contributor

@XuPeng-SH I am trying to join the source pk id (INT) with doc_id (INT).. I didn't use __mo_fake_pk_col to delete.

@tom-csf
Copy link
Author

tom-csf commented Nov 25, 2024

2.0-dev分支验证ok

@matrix-meow matrix-meow reopened this Nov 25, 2024
@cpegeric cpegeric assigned Ariznawlll and unassigned cpegeric Nov 28, 2024
@aressu1985 aressu1985 added the severity/s0 Extreme impact: Cause the application to break down and seriously affect the use label Nov 29, 2024
@mergify mergify bot closed this as completed in #20230 Nov 29, 2024
@mergify mergify bot closed this as completed in 03635a8 Nov 29, 2024
@matrix-meow matrix-meow reopened this Nov 29, 2024
@Ariznawlll
Copy link
Contributor

testing

@Ariznawlll
Copy link
Contributor

2.0-dev: 4b6c0c1

测试case:
load tpch 1g data to tpch_1g database
create table nation3 like nation;
insert into nation3 select * from nation;
set experimental_fulltext_index=1;
create fulltext index fdx9 on nation3(N_COMMENT);
delete from nation3 where n_nationkey = 10;
image

@Ariznawlll
Copy link
Contributor

image main测试通过

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
phase/testing severity/s0 Extreme impact: Cause the application to break down and seriously affect the use
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants