-
Notifications
You must be signed in to change notification settings - Fork 16.3k
[AIRFLOW-7034] Remove feature: Assigning Dag to task using Bitshift Op #7685
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
Conversation
zhongjiajie
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code look good to me, but have some minor suggest here
|
I think removing features like this one should be mentioned in |
Make sence |
…ing Bitshift Operator
Agree, fixed |
…task using Bitshift Operator
|
FYI, CI failed without more detail, should restart it to retest |
|
Restarted |
Codecov Report
@@ Coverage Diff @@
## master #7685 +/- ##
========================================
- Coverage 86.99% 86.7% -0.3%
========================================
Files 904 904
Lines 43728 43728
========================================
- Hits 38043 37916 -127
- Misses 5685 5812 +127
Continue to review full report at Codecov.
|
It is possible to assign a task to the dag using the bitshift operators, however it doesn't pick up default_args when done this way https://issues.apache.org/jira/browse/AIRFLOW-883:
Issue link: AIRFLOW-7034
Make sure to mark the boxes below before creating PR: [x]
[AIRFLOW-NNNN]. AIRFLOW-NNNN = JIRA ID** For document-only changes commit message can start with
[AIRFLOW-XXXX].In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.
Read the Pull Request Guidelines for more information.