provide a better hint if a table doesn't exist

[bharatnc]

Changelog category (leave one):

• Improvement

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):

Better hints when a table doesn't exist.

When a table doesn't exist, search if the table exists in other databases and include the database and table in the hint. For example:

SELECT * FROM views;

Received exception from server (version 23.11.1):
Code: 60. DB::Exception: Received from localhost:9000. DB::Exception: Table default.VIEWS does not exist. Maybe you meant INFORMATION_SCHEMA.VIEWS?. (UNKNOWN_TABLE)

DROP TABLE query_log;

Received exception from server (version 23.11.1):
Code: 60. DB::Exception: Received from localhost:9000. DB::Exception: Table default.query_log does not exist. Maybe you meant system.query_log?. (UNKNOWN_TABLE)

Related to: #51168

Information about CI checks: https://clickhouse.com/docs/en/development/continuous-integration/

[robot-clickhouse-ci-1]

This is an automated comment for commit c9f35a8 with description of existing statuses. It's updated for the latest CI running

❌ Click here to open a full report in a separate page

Successful checks

Check name	Description	Status
AST fuzzer	Runs randomly generated queries to catch program errors. The build type is optionally given in parenthesis. If it fails, ask a maintainer for help	✅ success
CI running	A meta-check that indicates the running CI. Normally, it's in success or pending state. The failed status indicates some problems with the PR	✅ success
ClickBench	Runs [ClickBench](https://github.com/ClickHouse/ClickBench/) with instant-attach table	✅ success
ClickHouse build check	Builds ClickHouse in various configurations for use in further steps. You have to fix the builds that fail. Build logs often has enough information to fix the error, but you might have to reproduce the failure locally. The cmake options can be found in the build log, grepping for cmake. Use these options and follow the general build process	✅ success
Compatibility check	Checks that clickhouse binary runs on distributions with old libc versions. If it fails, ask a maintainer for help	✅ success
Docker image for servers	The check to build and optionally push the mentioned image to docker hub	✅ success
Fast test	Normally this is the first check that is ran for a PR. It builds ClickHouse and runs most of stateless functional tests, omitting some. If it fails, further checks are not started until it is fixed. Look at the report to see which tests fail, then reproduce the failure locally as described here	✅ success
Flaky tests	Checks if new added or modified tests are flaky by running them repeatedly, in parallel, with more randomization. Functional tests are run 100 times with address sanitizer, and additional randomization of thread scheduling. Integrational tests are run up to 10 times. If at least once a new test has failed, or was too long, this check will be red. We don't allow flaky tests, read the doc	✅ success
Install packages	Checks that the built packages are installable in a clear environment	✅ success
Mergeable Check	Checks if all other necessary checks are successful	✅ success
Performance Comparison	Measure changes in query performance. The performance test report is described in detail here. In square brackets are the optional part/total tests	✅ success
Push to Dockerhub	The check for building and pushing the CI related docker images to docker hub	✅ success
SQLTest	There's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS	✅ success
SQLancer	Fuzzing tests that detect logical bugs with SQLancer tool	✅ success
Sqllogic	Run clickhouse on the sqllogic test set against sqlite and checks that all statements are passed	✅ success
Stateful tests	Runs stateful functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc	✅ success
Stateless tests	Runs stateless functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc	✅ success
Style Check	Runs a set of checks to keep the code style clean. If some of tests failed, see the related log from the report	✅ success
Unit tests	Runs the unit tests for different release types	✅ success

Check name	Description	Status
Integration tests	The integration tests report. In parenthesis the package type is given, and in square brackets are the optional part/total tests	❌ failure
Stress test	Runs stateless functional tests concurrently from several clients to detect concurrency-related errors	❌ failure
Upgrade check	Runs stress tests on server version from last release and then tries to upgrade it to the version from the PR. It checks if the new server can successfully startup without any errors, crashes or sanitizer asserts	❌ failure

[bharatnc]

cc: @alexey-milovidov

[tavplubix]

The implementation kind of duplicates TableNameHints added in #49801
Should we enhance TableNameHints instead?

cc: @yariks5s

[tavplubix]

Also, does it allow bypassing SHOW_DATABASES/SHOW_TABLES restriction in RBAC?

[yariks5s]

The implementation kind of duplicates TableNameHints added in #49801 Should we enhance TableNameHints instead?

cc: @yariks5s

Yes, it is better to add this logic to TableNameHints so we will know that everything regarding hints is in the one place

[bharatnc]

The implementation kind of duplicates TableNameHints added in #49801 Should we enhance TableNameHints instead?
cc: @yariks5s

Yes, it is better to add this logic to TableNameHints so we will know that everything regarding hints is in the one place

Thank you for the reviewing. I will make the changes.