WeiYe-Jing/datax-web

datax-web中对于获取数据库中所有表名是最好可以直接模糊搜索，而不是后端全量查询再在前端查询

Open

#251 opened on Jul 23, 2020

View on GitHub
 (1 comment) (1 reaction) (0 assignees)Java (5,195 stars) (2,045 forks)batch import
good first issuenew featurevolunteer wanted

Description

我在生产环境中测试的时候发现，在任务构建的时候，获取数据库表名时，是后端代码是全量获取所有表，然后前端可以进行过滤，但是这种方式在生产环境中存在缺陷，比如我一个odps的生产库，里面有几千张表，这样获取的速度就特别的慢，可以参考一下： ResultSet resultSet = metaData.getTables(null, "schema", "%tablename%", null);的形式模糊获取表名，这样的速度会有所提升

Contributor guide

Tech stack
javasql
Domain
backenddatabaseperformance
Issue type
performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaSQLJDBC
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Locate the Java file where `metaData.getTables` is called, likely in a service class responsible for retrieving table metadata. Replace the existing call that fetches all tables with one that uses a LIKE pattern (e.g., `metaData.getTables(null, "schema", "%tablename%", null)`) to allow fuzzy matching on the backend. Also, update the API endpoint to accept a search parameter from the frontend and pass it to the backend query. Test the change with a database containing many tables to verify performance improvement.