Skip to content

Conversation

@zhongjiajie
Copy link
Member

  • Remove the duplicate end_date in template context
  • Reorder template context key to make ds together

Make sure you have checked all steps below.

Jira

Description

  • Here are some details about my PR, including screenshots of any UI changes:
  • Remove the duplicate end_date in template context
  • Reorder template context key to make ds together

Code Quality

  • Passes flake8

@zhongjiajie
Copy link
Member Author

zhongjiajie commented Jul 20, 2019

I'm not sure we need END_DATE in template context or not, but I can not find it in our code base and we already have end_date(lowercase) with the same values

@zhongjiajie zhongjiajie force-pushed the model_ti_rm_duplicate_end_date branch from 2520505 to c5cf73f Compare July 20, 2019 11:51
@BasPH
Copy link
Contributor

BasPH commented Jul 20, 2019

I'm all in for this change, but FYI I suggested to do the same + more variables a while ago which led to a discussion going around in circles: #5010 (mailing list thread: https://lists.apache.org/thread.html/a81b32efc95db41a5bf847ed03b64ae4d3e9c8a2cbeda1bdcf0eb2f5@%3Cdev.airflow.apache.org%3E).

I suggest to merge this PR and tackle the other variables one-by-one instead of one single PR.

@zhongjiajie
Copy link
Member Author

@BasPH Sorry, I don't read all dev mail list and don't know you submit related PR.

But I find out we still have strong opinions on which variable should be remove. But think it safe to remove the duplicate key end_date and END_DATE

I find out that some summary in mail list

We start by putting deprecation warnings on tables, latest_date, end_date and END_DATE and remove them in Airflow 2.0.

I think we still have end_date in template, so @deprecation is not necessary for this PR

Copy link
Member Author

@zhongjiajie zhongjiajie Jul 20, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And what do you think this change. At first I think template messy and all date variable should keep together, but I find out your PR like to keep them in alphabetical
Should I change them in alphabetical or keep them? @BasPH

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's reorder alphabetically and then merge 👍

* Remove the duplicate end_date in template context
* Reorder template context key to make ds together
@zhongjiajie zhongjiajie force-pushed the model_ti_rm_duplicate_end_date branch from c5cf73f to c14a52e Compare July 21, 2019 16:37
@zhongjiajie
Copy link
Member Author

Reorder template context alphabetically

Copy link
Contributor

@BasPH BasPH left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work!

@BasPH BasPH merged commit a2ec24a into apache:master Jul 22, 2019
@zhongjiajie
Copy link
Member Author

Thanks

@zhongjiajie zhongjiajie deleted the model_ti_rm_duplicate_end_date branch July 23, 2019 01:28
serkef pushed a commit to serkef/airflow that referenced this pull request Jul 24, 2019
…#5618)

* Remove the duplicate end_date in template context
* Reorder template context key to make ds together
wmorris75 pushed a commit to modmed-external/incubator-airflow that referenced this pull request Jul 29, 2019
…#5618)

* Remove the duplicate end_date in template context
* Reorder template context key to make ds together
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants