Because SQL statements can contain sensitive information, Databricks now masks query text in the following places: statement text in system.query.history returns
Because SQL statements can contain sensitive information, Databricks now masks query text in the following places: statement text in system.query.history returns
Reduces operational overhead and unlocks new capabilities for data teams on Databricks.
Because SQL statements can contain sensitive information, Databricks now masks query text in the following places: statement text in system.query.history returns