[Bug] dbtCore- With Each Select run the dbt is parsing and validating all the models databases and tables Causing too many API calls

[Amar1404]

Is this a new bug in dbt-core?

• I believe this is a new bug in dbt-core
• I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

Hi,
While i run dbt run --select dbt_model.sql here all the databases and tables of all the models reference in each run is hitting the glue catalog to validate the database exist causing the glue api to choke.

Expected Behavior

Hi,
While with each run dbt --select it should validate either just only the database in which the table is created.

Steps To Reproduce

1. create a multiple model on dbt
2. just run with dbt run --select model_name -d
3. In the logs you will see with every run the dbt run is calling information getdatabases calls to multiple database on which models are created

Relevant log output

Environment

- OS: LINUX
- Python: 3.9.10
- dbt: 1.9.1

Which database adapter are you using with dbt?

other (mention it in "Additional Context")

Additional Context

Using with dbt-athena or dbt-trino

[jeremyyeo]

Does --cache-selected-only give you what you need? https://docs.getdbt.com/reference/global-configs/cache#cache-population