moomindani commented on code in PR #74330: URL: https://github.com/apache/airflow/pull/74330#discussion_r4513413055
########## providers/databricks/docs/operators/submit_run.rst: ########## @@ -247,3 +247,39 @@ DatabricksSubmitRunDeferrableOperator Deferrable version of the :class:`~airflow.providers.databricks.operators.DatabricksSubmitRunOperator` operator. It allows to utilize Airflow workers more effectively using `new functionality introduced in Airflow 2.2.0 <https://airflow.apache.org/docs/apache-airflow/2.2.0/concepts/deferring.html#triggering-deferral>`_ + +Explicit assets Review Comment: This is appended after the `DatabricksSubmitRunDeferrableOperator` heading, so it renders as a subsection of the deferrable alias rather than of `DatabricksSubmitRunOperator`. Moving it up next to "Durable execution" (same `-` level) puts it under the operator. ########## providers/databricks/docs/operators/sql_statements.rst: ########## @@ -109,3 +109,46 @@ An example usage of the ``DatabricksSQLStatementsSensor`` is as follows: :language: python :start-after: [START howto_sensor_databricks_sql_statement] :end-before: [END howto_sensor_databricks_sql_statement] + +Explicit assets Review Comment: Both this section and "Mapped tasks and templated names" come after the `DatabricksSQLStatementsSensor` heading, so they render under the sensor. They describe the operator, so they belong after the operator's "Examples" section, before the sensor heading. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
