[MDEV-29430] 'Got error 1054 when reading table' on SELECT (Spider) Created: 2022-09-01 Updated: 2022-10-20 Resolved: 2022-10-20 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - Spider |
| Affects Version/s: | 10.4, 10.5, 10.6, 10.7, 10.8, 10.9, 10.10, 10.11 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Roel Van de Paar | Assignee: | Nayuta Yanagisawa (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||
| Description |
|
Please update '../socket.sock' to actual path on your instance, or similar (host/port may or may not work)
Leads to (CLI):
And (Error log):
Bug confirmed present in: |
| Comments |
| Comment by Ramesh Sivaraman [ 2022-09-01 ] | ||||||
|
Reproduced the issue on QA box
| ||||||
| Comment by Roel Van de Paar [ 2022-09-20 ] | ||||||
|
I also had a look into another testcase showing ERROR 1146 (Table '...' doesn't exist), however that issue proved to be where the underlying table was deleted, but the Spider table was left, in which case it would seem normal to receive such an error when accessing the Spider table (and the error referred to the underlying table, which is correct). As such, I have filtered error 1146 from the runs. |