Hi I m loading DBT assets and getting error because I think

Question

Hi I m loading DBT assets and getting error because I think I have a schema name in DBT that is prohibited in dagster How to get around this ```dagster core errors DagsterInvalidDefinitionError meta is not a valid name in Dagster It conflicts with a Dagster or python reserved keyword dbt assets = load assets from dbt project File root cache pypoetry virtualenvs l2 check pipeline VA82Wl8V py3 8 lib python3 8 site packages dagster dbt asset defs py line 364 in load assets from dbt project return load assets from dbt manifest File root cache pypoetry virtualenvs l2 check pipeline VA82Wl8V py3 8 lib python3 8 site packages dagster dbt asset defs py line 433 in load assets from dbt manifest dbt assets def = dbt nodes to assets File root cache pypoetry virtualenvs l2 check pipeline VA82Wl8V py3 8 lib python3 8 site packages dagster dbt asset defs py line 272 in dbt nodes to assets return AssetsDefinition File root cache pypoetry virtualenvs l2 check pipeline VA82Wl8V py3 8 lib python3 8 site packages dagster core asset defs assets py line 85 in init self group names by key key = validate group name group name File root cache pypoetry virtualenvs l2 check pipeline VA82Wl8V py3 8 lib python3 8 site packages dagster core definitions utils py line 122 in validate group name return check valid name group name File root cache pypoetry virtualenvs l2 check pipeline VA82Wl8V py3 8 lib python3 8 site packages dagster core definitions utils py line 56 in check valid name raise DagsterInvalidDefinitionError ```

Harpal · Answer

I would rename it from `meta` to something that isn t a prohibited word and try again Maybe something like `meta task`

Eric Larson · Answer

Actuallty sorry I don t have a schema named meta I just assumed I did from the error message I do have some tables models that have the prefix `meta` like `meta county` but I can t find what is causing this error I have successfully loaded a subset of the models in the DBT repo I guess I could keep trying different subsets until I find the one that breaks it

Eric Larson · Answer

So it turns out I had a subfolder in the `models` directory named `meta` and renaming it made dagster happy Looks like dagster was using the folder name as a Group name for the models in it

sandy · Answer

Glad you were able to figure this out Eric I filed an issue to remove this limitation <https github com dagster io dagster issues 8534>

Eric Larson · Answer

+1