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.

Sign up for GitHub

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

Jump to bottom

对于 hot inventory中的 hint 请问哪里有解释 #62

Open
shenlan219 opened this issue Jun 21, 2017 · 1 comment
Open

对于 hot inventory中的 hint 请问哪里有解释 #62

shenlan219 opened this issue Jun 21, 2017 · 1 comment

Comments

@shenlan219
Copy link

在 “ AliSQL秒杀场景测试报告样例 ”中的hint，COMMIT_ON_SUCCESS ROLLBACK_ON_FAIL QUEUE_ON_PK 1 TARGET_AFFECT_ROW 1
能否解释下，特别是 QUEUE_ON_PK 1 TARGET_AFFECT_ROW 1 两个值，似乎影响着队列的性能
@zhaiwx1987
Copy link

TARGET_AFFECT_ROW 1 means if the number of affected rows doesn't match the hint, it will report an error and consider the statement as failed. If the statement is succeed, COMMIT_ON_SUCCESS means the transaction will be committed automatically, otherwise the transaction will be automatically rollback if specifying ROLLBACK_ON_FAIL.

QUEUE_ON_PK specifies the value of PK. The statements with same primary key will be queued and executed one by one.

fungo pushed a commit that referenced this issue May 1, 2018
[bugfix] Issue: #62 alter TokuDB table comment rebuild whole engine data
349aa36 
Alter TokuDB table comment should not using copying algorithm and
rebuild whole engine data, only FRM definition should be changed.

Make `ha_tokudb::check_if_supported_inplace_alter()` return
`HA_ALTER_INPLACE_EXCLUSIVE_LOCK` while altering comment, and mysql
server will invoke `ha_tokudb::inplace_alter_table` which will do
nothing for altering comment.

Besides table comment, there are many other create options that
should be ignored by TokuDB, and they are all handled in this patch.

Btw, this patch has been pushed to TokuDB upstream.

This patch also contains a postfix for bug#88847, which handles
cases when UK or Key with auto-inc fileld is invisible.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zhaiwx1987 @shenlan219