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

tidb meets ERROR 1105 (HY000): Can't find column db.table.col in schema Column: [Column#235] Unique key: [] when use tikv read engine #48841

Closed
AkiraXie opened this issue Nov 23, 2023 · 2 comments
Labels
found/automation Found by automation tests may-affects-5.3 This bug maybe affects 5.3.x versions. may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-6.1 may-affects-6.5 may-affects-7.1 may-affects-7.5 severity/major sig/planner SIG: Planner type/bug The issue is confirmed as a bug.

Comments

@AkiraXie
Copy link

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

set tidb_isolation_read_engines = 'tikv';
select count(*) from db.table;

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

3. What did you see instead (Required)

  1. ERROR 1105 (HY000): Can't find column db.table.col in schema Column: [Column#235] Unique key: []
  2. related log:
    [session.go:2163] ["compile SQL failed"] [conn=2095763720541056355] [error="Can't find column db.table.col in schema Column: [Column#235] Unique key: []"] [SQL="select count() from table"]
    [conn.go:1152] ["command dispatched failed"] [conn=2095763720541056355] [connInfo="id:2095763720541056355, addr:10.233.79.32:43575 status:11, collation:utf8mb4_general_ci, user:root"] [command=Query] [status="inTxn:1, autocommit:1"] [sql="select count() from table"] [txn_mode=PESSIMISTIC] [timestamp=437772032938344571] [err="Can't find column db.table.col in schema Column: [Column#235] Unique key: []\ngithub.com/pingcap/tidb/expression.(*Column).resolveIndices\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/expression/column.go:534\ngithub.com/pingcap/tidb/expression.(*Column).ResolveIndices\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/expression/column.go:527\ngithub.com/pingcap/tidb/planner/core.(*basePhysicalAgg).ResolveIndices\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/planner/core/resolve_indices.go:422\ngithub.com/pingcap/tidb/planner/core.(*PhysicalIndexReader).ResolveIndices\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/planner/core/resolve_indices.go:300\ngithub.com/pingcap/tidb/planner/core.(*basePhysicalPlan).ResolveIndices\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/planner/core/resolve_indices.go:710\ngithub.com/pingcap/tidb/planner/core.(*physicalSchemaProducer).ResolveIndices\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/planner/core/resolve_indices.go:699\ngithub.com/pingcap/tidb/planner/core.(*basePhysicalAgg).ResolveIndices\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/planner/core/resolve_indices.go:416\ngithub.com/pingcap/tidb/planner/core.(*basePhysicalPlan).ResolveIndices\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/planner/core/resolve_indices.go:710\ngithub.com/pingcap/tidb/planner/core.(*physicalSchemaProducer).ResolveIndices\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/planner/core/resolve_indices.go:699\ngithub.com/pingcap/tidb/planner/core.(*PhysicalProjection).ResolveIndices\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/planner/core/resolve_indices.go:42\ngithub.com/pingcap/tidb/planner/core.physicalOptimize\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/planner/core/optimizer.go:843\ngithub.com/pingcap/tidb/planner/core.DoOptimize\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/planner/core/optimizer.go:296\ngithub.com/pingcap/tidb/planner.optimize\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/planner/optimize.go:398\ngithub.com/pingcap/tidb/planner.Optimize\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/planner/optimize.go:245\ngithub.com/pingcap/tidb/executor.(*Compiler).Compile\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/executor/compiler.go:116\ngithub.com/pingcap/tidb/session.(*session).ExecuteStmt\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/session/session.go:2151\ngithub.com/pingcap/tidb/server.(*TiDBContext).ExecuteStmt\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/server/driver_tidb.go:233\ngithub.com/pingcap/tidb/server.(*clientConn).handleStmt\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/server/conn.go:2093\ngithub.com/pingcap/tidb/server.(*clientConn).handleQuery\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/server/conn.go:1943\ngithub.com/pingcap/tidb/server.(*clientConn).dispatch\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/server/conn.go:1374\ngithub.com/pingcap/tidb/server.(*clientConn).Run\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/server/conn.go:1123\ngithub.com/pingcap/tidb/server.(*Server).onConn\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/server/server.go:624\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1594"]

4. What is your TiDB version? (Required)

Release Version: v6.5.0-alpha
Edition: Community
Git Commit Hash: 6a4b909
Git Branch: heads/refs/tags/v6.5.0-alpha
UTC Build Time: 2022-12-01 10:57:44
GoVersion: go1.19.3
Race Enabled: false
TiKV Min Version: 6.2.0-alpha
Check Table Before Drop: false
Store: tikv

@AkiraXie AkiraXie added the type/bug The issue is confirmed as a bug. label Nov 23, 2023
@AkiraXie
Copy link
Author

/severity major
/found automation

@ti-chi-bot ti-chi-bot bot added severity/major found/automation Found by automation tests may-affects-5.3 This bug maybe affects 5.3.x versions. may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-6.1 may-affects-6.5 may-affects-7.1 may-affects-7.5 labels Nov 23, 2023
@AkiraXie
Copy link
Author

after pr #39555 merged, the issue can't be seen

@jebter jebter added the sig/planner SIG: Planner label May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
found/automation Found by automation tests may-affects-5.3 This bug maybe affects 5.3.x versions. may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-6.1 may-affects-6.5 may-affects-7.1 may-affects-7.5 severity/major sig/planner SIG: Planner type/bug The issue is confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

2 participants