jdlong
February 12, 2019, 9:24pm
13
Hey if you're interested in Airflow, you might want to pop into their git hub issues section and say you're interested in an R operator. I've nudged them to reopen the issue.
apache:master ← briandconnelly:master
opened 09:30PM - 08 Mar 18 UTC
Make sure you have checked _all_ steps below.
### 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-2193
### Description
- [x] Here are some details about my PR, including screenshots of any UI changes:
The ROperator allows tasks to be specified using the R programming
language for statistical computing. Tasks can be specified either
as R operations or using a source file. Optionally, the last line of
output can be pushed to an Xcom.
ROperator requires [rpy2](https://rpy2.readthedocs.io/) (and R)
Data can be passed to R using either the environment or through
templating.
### Tests
- [x] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason:
Several tests are specified in `tests/contrib/operators/test_r_operator.py`, which I cover most of the exposed features
### 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
2. Subject is limited to 50 characters
3. Subject does not end with a period
4. Subject uses the imperative mood ("add", not "adding")
5. Body wraps at 72 characters
6. Body explains "what" and "why", not "how"
- [x] Passes `git diff upstream/master -u -- "*.py" | flake8 --diff`
3 Likes