Skip to content

[fix](case) check_hash_bucket_table: quote db/table identifiers#64510

Open
shuke987 wants to merge 1 commit into
apache:branch-4.1from
shuke987:fix-check-hash-bucket-table-backtick
Open

[fix](case) check_hash_bucket_table: quote db/table identifiers#64510
shuke987 wants to merge 1 commit into
apache:branch-4.1from
shuke987:fix-check-hash-bucket-table-backtick

Conversation

@shuke987

Copy link
Copy Markdown
Collaborator

Problem

This global check iterates over all databases/tables and builds statements like show create table ${tblName} without backticks. When another suite leaves behind a table named with a reserved word (e.g. order), the statement becomes show create table ordermismatched input 'order', which fails the whole check. This only triggers under the full P0 pipeline (cross-suite residue), not when the suite runs in isolation.

Fix

Backtick all db / table / partition identifiers (use, desc, show create table, show partitions, show replica status, and the select ... from db.table).

Verification

Ran the suite on a branch-4.1 local cluster — passes.

🤖 Generated with Claude Code

This global check iterates over all databases/tables and builds statements like
`show create table ${tblName}` without backticks. When another suite leaves behind a
table named with a reserved word (e.g. `order`), the statement becomes
`show create table order` -> `mismatched input 'order'`, failing the whole check.
This only triggers under the full pipeline (cross-suite residue), not in isolation.
Backtick all db/table/partition identifiers.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@shuke987 shuke987 requested a review from yiguolei as a code owner June 15, 2026 06:53
@hello-stephen

Copy link
Copy Markdown
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@shuke987

Copy link
Copy Markdown
Collaborator Author

run buildall

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants