[
https://issues.apache.org/jira/browse/AIRFLOW-5753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16959377#comment-16959377
]
ASF GitHub Bot commented on AIRFLOW-5753:
-----------------------------------------
bskim45 commented on pull request #6428: [AIRFLOW-5753] Add
DailyLatestOnlyOperator
URL: https://github.com/apache/airflow/pull/6428
### Jira
- [x] My PR addresses the following [Airflow
Jira](https://issues.apache.org/jira/browse/AIRFLOW/) issues and references
them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
- https://issues.apache.org/jira/browse/AIRFLOW-5753
- In case you are fixing a typo in the documentation you can prepend your
commit with \[AIRFLOW-XXX\], code changes always need a Jira issue.
- In case you are proposing a fundamental code change, you need to create
an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)).
- In case you are adding a dependency, check if the license complies with
the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
### Description
- [x] Here are some details about my PR, including screenshots of any UI
changes:
In addition to LatestOnlyOperator, DailyLatestOnlyOperator is for cases that
we need to run only the latest run in the series of task run, but to ensure
that the task is run at least once in a day.
This is useful when we scrape external data from third-parties on an hourly
basis/for multiple times in a day to keep data up-to-date. If the DAG is paused
for several days, we want to avoid multiple runs in a day, but still want to
ensure data is filled in every daily window.
### Tests
- [x] My PR adds the following unit tests __OR__ does not need testing for
this extremely good reason:
`test_daily_latest_only_operator.py` added
### Commits
- [x] My commits all reference Jira issues in their subject lines, and I
have squashed multiple commits if they address the same issue. In addition, my
commits follow the guidelines from "[How to write a good git commit
message](http://chris.beams.io/posts/git-commit/)":
1. Subject is separated from body by a blank line
1. Subject is limited to 50 characters (not including Jira issue reference)
1. Subject does not end with a period
1. Subject uses the imperative mood ("add", not "adding")
1. Body wraps at 72 characters
1. Body explains "what" and "why", not "how"
### Documentation
- [x] In case of new functionality, my PR adds documentation that describes
how to use it.
- All the public functions and the classes in the PR contain docstrings
that explain what it does
- If you implement backwards incompatible changes, please leave a note in
the [Updating.md](https://github.com/apache/airflow/blob/master/UPDATING.md) so
we can assign it to a appropriate release
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Add DailyLatestOnlyOperator
> ---------------------------
>
> Key: AIRFLOW-5753
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5753
> Project: Apache Airflow
> Issue Type: New Feature
> Components: operators
> Affects Versions: 1.10.5
> Reporter: Bumsoo Kim
> Assignee: Bumsoo Kim
> Priority: Major
>
> In addition to {{LatestOnlyOperator}}, {{DailyLatestOnlyOperator}} is for
> cases that we need to run only the latest run in the series of task run, but
> to ensure that the task is run at least once in a day.
> This is useful when we scrape external data from third-parties on an hourly
> basis/for multiple times in a day to keep data up-to-date. If the DAG is
> paused for several days, we want to avoid multiple runs in a day, but still
> want to ensure data is filled in every daily window.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
