Skip to content

branch-4.1: [feat](catalog) Support include_table_list property and refactor lower_case_database/table_names for external catalog (#60580)#61498

Merged
yiguolei merged 1 commit intoapache:branch-4.1from
morningman:41_bp60580
Mar 19, 2026

Conversation

@morningman
Copy link
Contributor

bp #60580

…r_case_database/table_names for external catalog (apache#60580)

Add `include_table_list` catalog property to allow users to specify an
explicit list of tables (in "db.tbl" format) to include when listing
tables from external catalogs such as HMS. When set, only the specified
tables are returned instead of fetching the full table list from the
remote metastore, which can significantly reduce metadata overhead for
catalogs with a large number of tables.
Sometimes calling `getAllTables` from HMS will timeout, can use this to
avoid.

2. Introduce `lower_case_database_names` catalog property and perform a
unified refactoring together with `lower_case_table_names`:

  - 0: case-sensitive (default)
  - 1: database names are stored as lowercase
  - 2: database names are compared case-insensitively

  - Fix display behavior when lower_case_database_names or
    lower_case_table_names = 2: database and table names are now
    displayed using their original case from the remote metastore,
    rather than the lowercased form.
  - Fix case-sensitivity handling in SQL statements: when referencing
    database or table names in queries, the case-sensitivity behavior
    now correctly respects the corresponding parameter configuration.
  - Fix case-sensitivity handling in SHOW statements to properly
    apply the configured case-sensitivity rules.
@morningman morningman requested a review from yiguolei as a code owner March 18, 2026 18:24
@hello-stephen
Copy link
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?

@morningman
Copy link
Contributor Author

run buildall

@hello-stephen
Copy link
Contributor

FE UT Coverage Report

Increment line coverage 65.73% (117/178) 🎉
Increment coverage report
Complete coverage report

@yiguolei yiguolei merged commit d807ecc into apache:branch-4.1 Mar 19, 2026
26 of 29 checks passed
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.

3 participants