Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CT-2409] [Bug] FQN selection for versioned models in subdirectory #7348

Closed
jtcohen6 opened this issue Apr 13, 2023 · 0 comments · Fixed by #7351
Closed

[CT-2409] [Bug] FQN selection for versioned models in subdirectory #7348

jtcohen6 opened this issue Apr 13, 2023 · 0 comments · Fixed by #7351
Assignees
Labels
bug Something isn't working model_versions

Comments

@jtcohen6
Copy link
Contributor

jtcohen6 commented Apr 13, 2023

If a versioned model is nested in one or more subdirectories, it can't be selected by name, v{v}, etc.

Expected behavior:

dbt list -s dim_customers    --> all
dbt list -s dim_customers.*  --> all
dbt list -s dim_customers.v1 --> v1 only
dbt list -s *.v1             --> any model with v1

Current behavior:
None of the above work, but it does work when I add in the * wildcards:

dbt ls -s *.dim_customers.*  --> all
dbt ls -s *.dim_customers.v1 --> v1 only

Weirdly, I could've sworn this was working when I was trying out #7287. Worth adding some tests. Realized that this only happens for a model defined in a subdirectory, rather than top-level in the models/ folder.

@github-actions github-actions bot changed the title [Bug] FQN selection for versioned models [CT-2409] [Bug] FQN selection for versioned models Apr 13, 2023
@MichelleArk MichelleArk self-assigned this Apr 13, 2023
@jtcohen6 jtcohen6 changed the title [CT-2409] [Bug] FQN selection for versioned models [CT-2409] [Bug] FQN selection for versioned models in subdirectory Apr 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working model_versions
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants