You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/04/24 10:10:00 UTC

[jira] [Commented] (AIRFLOW-4228) DatabricksRunNowOperator does not show up under airflow docs

    [ https://issues.apache.org/jira/browse/AIRFLOW-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16824978#comment-16824978 ] 

ASF GitHub Bot commented on AIRFLOW-4228:
-----------------------------------------

Tomme commented on pull request #5171: [AIRFLOW-4228] DatabricksRunNowOperator does not show up under airflo…
URL: https://github.com/apache/airflow/pull/5171
 
 
   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-4228
   
   ### Description
   
   - [x] Updated `integration.rst` to include `DatabricksRunNowOperator`.
   
   ### Tests
   
   - [x] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason:
     - Documentation update, no tests needed.
   
   ### 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:
users@infra.apache.org


> DatabricksRunNowOperator does not show up under airflow docs
> ------------------------------------------------------------
>
>                 Key: AIRFLOW-4228
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-4228
>             Project: Apache Airflow
>          Issue Type: Bug
>            Reporter: Thomas Dziedzic
>            Assignee: Thomas Elvey
>            Priority: Trivial
>
> [https://airflow.apache.org/_modules/airflow/contrib/operators/databricks_operator.html] contains DatabricksRunNowOperator but when you visit [https://airflow.apache.org/integration.html?highlight=databricks#databricks] there is no mention of the DatabricksRunNowOperator even though it is available and working.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)