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

ScalarFunction Unspecified is not supported in batch mode #30115

Closed
aytrack opened this issue Nov 24, 2021 · 2 comments
Closed

ScalarFunction Unspecified is not supported in batch mode #30115

aytrack opened this issue Nov 24, 2021 · 2 comments
Labels
severity/major sig/transaction SIG:Transaction type/bug The issue is confirmed as a bug.

Comments

@aytrack
Copy link
Contributor

aytrack commented Nov 24, 2021

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

CREATE TABLE g(c INTEGER, b INTEGER);
CREATE TABLE t(a INTEGER);
UPDATE t SET a=1 WHERE EXISTS(SELECT b FROM g WHERE 1 NOT LIKE c FOR UPDATE);
DROP TABLE g, t;

first find in #29905 merge Integration test https://ci.pingcap.net/blue/organizations/jenkins/tidb_ghpr_integration_common_test/detail/tidb_ghpr_integration_common_test/7898/pipeline

2021-11-24T09:15:39.029Z] time="2021-11-24T17:15:38+08:00" level=error msg="run test [update] err: sql:UPDATE t SET a=1 WHERE EXISTS(SELECT b FROM g WHERE 1 NOT LIKE c FOR UPDATE);: run \"UPDATE t SET a=1 WHERE EXISTS(SELECT b FROM g WHERE 1 NOT LIKE c FOR UPDATE);\" at line 348 err Error 1105: other error: [components/tidb_query_expr/src/lib.rs:711]: ScalarFunction Unspecified is not supported in batch mode"

2. What did you expect to see? (Required)

3. What did you see instead (Required)

4. What is your TiDB version? (Required)

@aytrack aytrack added type/bug The issue is confirmed as a bug. sig/transaction SIG:Transaction severity/major labels Nov 24, 2021
@aytrack
Copy link
Contributor Author

aytrack commented Nov 24, 2021

@github-actions
Copy link

Please check whether the issue should be labeled with 'affects-x.y' or 'fixes-x.y.z', and then remove 'needs-more-info' label.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity/major sig/transaction SIG:Transaction type/bug The issue is confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

2 participants