I'm in support of adding a `DatabricksRunNowOperator`. I don't think sharing logic through a base `DatabricksOperator` is the way to go though since we may want to add other operators which do not rely on the run polling logic. I'd much prefer to lift the run polling logic out of the class as a helper function. @isknight is working on something like this for his use case.
[ Full content available at: https://github.com/apache/incubator-airflow/pull/2932 ] This message was relayed via gitbox.apache.org for [email protected]
