Databricks SDK for JavaScript
    Preparing search index...

    Variable DataSecurityModeConst

    DataSecurityMode: {
        DATA_SECURITY_MODE_AUTO: "DATA_SECURITY_MODE_AUTO";
        DATA_SECURITY_MODE_DEDICATED: "DATA_SECURITY_MODE_DEDICATED";
        DATA_SECURITY_MODE_STANDARD: "DATA_SECURITY_MODE_STANDARD";
        LEGACY_PASSTHROUGH: "LEGACY_PASSTHROUGH";
        LEGACY_SINGLE_USER: "LEGACY_SINGLE_USER";
        LEGACY_SINGLE_USER_STANDARD: "LEGACY_SINGLE_USER_STANDARD";
        LEGACY_TABLE_ACL: "LEGACY_TABLE_ACL";
        NONE: "NONE";
        SINGLE_USER: "SINGLE_USER";
        USER_ISOLATION: "USER_ISOLATION";
    } = ...

    Data security mode decides what data governance model to use when accessing data from a cluster.

    • DATA_SECURITY_MODE_AUTO: will choose the most appropriate access mode depending on your compute configuration.
    • DATA_SECURITY_MODE_STANDARD: A secure cluster that can be shared by multiple users. Cluster users are fully isolated so that they cannot see each other’s data and credentials. Most data governance features are supported in this mode. But programming languages and cluster features might be limited.
    • DATA_SECURITY_MODE_DEDICATED: A secure cluster that can only be exclusively used by a single user specified in single_user_name. Most programming languages, cluster features and data governance features are available in this mode.

    The following modes are legacy aliases for the above modes:

    • USER_ISOLATION: Legacy alias for DATA_SECURITY_MODE_STANDARD.
    • SINGLE_USER: Legacy alias for DATA_SECURITY_MODE_DEDICATED.

    The following modes are deprecated starting with Databricks Runtime 15.0 and will be removed for future Databricks Runtime versions:

    • LEGACY_TABLE_ACL: This mode is for users migrating from legacy Table ACL clusters.
    • LEGACY_PASSTHROUGH: This mode is for users migrating from legacy Passthrough on high concurrency clusters.
    • LEGACY_SINGLE_USER: This mode is for users migrating from legacy Passthrough on standard clusters.
    • LEGACY_SINGLE_USER_STANDARD: This mode provides a way that doesn’t have UC nor passthrough enabled.

    Type Declaration

    • ReadonlyDATA_SECURITY_MODE_AUTO: "DATA_SECURITY_MODE_AUTO"

      Databricks will choose DATA_SECURITY_MODE_STANDARD or DATA_SECURITY_MODE_DEDICATED depending on the compute configuration.

    • ReadonlyDATA_SECURITY_MODE_DEDICATED: "DATA_SECURITY_MODE_DEDICATED"

      A secure cluster that can only be exclusively used by a single user specified in single_user_name. Most programming languages, cluster features and data governance features are available in this mode.

    • ReadonlyDATA_SECURITY_MODE_STANDARD: "DATA_SECURITY_MODE_STANDARD"

      A secure cluster that can be shared by multiple users. Cluster users are fully isolated so that they cannot see each other's data and credentials. Most data governance features are supported in this mode. But programming languages and cluster features might be limited.

    • ReadonlyLEGACY_PASSTHROUGH: "LEGACY_PASSTHROUGH"

      This mode is for users migrating from legacy Passthrough on high concurrency clusters.

    • ReadonlyLEGACY_SINGLE_USER: "LEGACY_SINGLE_USER"

      This mode is for users migrating from legacy Passthrough on standard clusters.

    • ReadonlyLEGACY_SINGLE_USER_STANDARD: "LEGACY_SINGLE_USER_STANDARD"

      This is mode where single user is enforced but no actual security feature enabled.

    • ReadonlyLEGACY_TABLE_ACL: "LEGACY_TABLE_ACL"

      This mode is for users migrating from legacy Table ACL clusters.

    • ReadonlyNONE: "NONE"

      No security isolation for multiple users sharing the cluster. Data governance features are not available in this mode.

    • ReadonlySINGLE_USER: "SINGLE_USER"

      Legacy alias for DATA_SECURITY_MODE_DEDICATED.

    • ReadonlyUSER_ISOLATION: "USER_ISOLATION"

      Legacy alias for DATA_SECURITY_MODE_STANDARD.

    Settings

    Member Visibility