-
Notifications
You must be signed in to change notification settings - Fork 159
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
Model selection "plus" operator not properly parsed when selecting tags #823
Comments
🤖 That's a great initiative! Your willingness to take a stab at adding this functionality to This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research. Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant. If you want to continue the conversation, start your reply with @dosu-bot. |
Thanks @enkeboll for opening this issue!
That would be great, thanks! Let us know if you need any support. |
Any update on this? We just hit the same issue 🥲 |
I personally haven't started work on this yet, though it's still in my backlog. |
@enkeboll @danielvdende, would you have bandwidth to work on this? |
Would it be possible to for the development team to pick this up? We are making use of custom node renderers for sources (sensor to wait on loading task) and exposures (operator triggering refresh in BI-tool), but schedule-related tags only make sense in case models. We would like to run models tagged daily in a daily Airflow DAG, models tagged weekly in a weekly DAG, etc. We have quite extensive workarounds for now to make this work, but would like to get rid of them. |
It seems @mvictoria is solving the issue in #1150 🎉 |
Migrating an issue raised in the
#airflow-dbt
slack org:Basically, the "plus" operator isn't properly parsed when used with tags. So
tag:every-hour
works but+tag:every-hour
ortag:every-hour+
result in empty graphs. We use this syntax in our DBT Cloud scheduled jobs, even though it isn't explicitly called out in the DBT docs:I'm happy to try to take a stab at adding this functionality to selector.py, unless there's a reason to hold off.
The text was updated successfully, but these errors were encountered: