Skip to content

2.0.2.1 oracle data format - #26112

Closed
zy-kkk wants to merge 1 commit into
apache:release-2.0.2.1from
zy-kkk:zy-kkk-patch-1
Closed

2.0.2.1 oracle data format#26112
zy-kkk wants to merge 1 commit into
apache:release-2.0.2.1from
zy-kkk:zy-kkk-patch-1

Conversation

@zy-kkk

Copy link
Copy Markdown
Member

Proposed changes

Issue Number: close #xxx

Further comments

If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...

@github-actionsgithub-actionsBot added the area/planner Issues or PRs related to the query planner label Oct 30, 2023
@zy-kkk
zy-kkk deleted the zy-kkk-patch-1 branch October 31, 2023 02:37
yiguolei pushed a commit to Gabriel39/incubator-doris that referenced this pull request Jun 16, 2026
Issue Number: closeapache#26112
Related PR: None
Problem Summary: Querying information_schema.columns with an external system table name such as table can call FrontendServiceImpl.getTableNames with the table name as a pattern. The MySQL pattern converter rejected '$' as a forbidden regex character, so the FE thrift service threw an internal getTableNames error before metadata resolution. This change treats '$' as a literal character in MySQL patterns by escaping it for the generated Java regex, allowing system table names to be matched safely.
Fixes metadata lookup for table names containing '$', including external system tables such as table.
- Test: Manual test
- Ran git diff --check and git diff --cached --check.
- Tried ./run-fe-ut.sh --run org.apache.doris.common.PatternMatcherTest, but the local environment only has JDK 11 and the script requires JDK 17.
- Behavior changed: Yes. MySQL pattern matching now allows '$' as a literal table-name character.
- Does this need documentation: No
(cherry picked from commit 14c184f)
morningman pushed a commit to Gabriel39/incubator-doris that referenced this pull request Jun 24, 2026
Issue Number: closeapache#26112
Related PR: None
Problem Summary: Querying information_schema.columns with an external system table name such as table can call FrontendServiceImpl.getTableNames with the table name as a pattern. The MySQL pattern converter rejected '$' as a forbidden regex character, so the FE thrift service threw an internal getTableNames error before metadata resolution. This change treats '$' as a literal character in MySQL patterns by escaping it for the generated Java regex, allowing system table names to be matched safely.
Fixes metadata lookup for table names containing '$', including external system tables such as table.
- Test: Manual test
- Ran git diff --check and git diff --cached --check.
- Tried ./run-fe-ut.sh --run org.apache.doris.common.PatternMatcherTest, but the local environment only has JDK 11 and the script requires JDK 17.
- Behavior changed: Yes. MySQL pattern matching now allows '$' as a literal table-name character.
- Does this need documentation: No
(cherry picked from commit 14c184f)
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/plannerIssues or PRs related to the query planner

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@zy-kkk@morningman