< Back

Remove-DatabricksLibrary

Sat Jan 11, 2020 10:04 am

NAME Remove-DatabricksLibrary



SYNOPSIS

Remove a library from a cluster - note the cluster must be restarted to complete the uninstall (this command will

NOT restart the cluster for you)





SYNTAX

Remove-DatabricksLibrary [[-BearerToken] <String>] [[-Region] <String>] [-ClusterId] <String> [-LibraryType]

<String> [-LibrarySettings] <String> [<CommonParameters>]





DESCRIPTION

Remove a library from a cluster - note the cluster must be restarted to complete the uninstall (this command will

NOT restart the cluster for you)





PARAMETERS

-BearerToken <String>

Your Databricks Bearer token to authenticate to your workspace (see User Settings in Datatbricks WebUI)



Required? false

Position? 1

Default value

Accept pipeline input? false

Accept wildcard characters? false



-Region <String>

Azure Region - must match the URL of your Databricks workspace, example northeurope



Required? false

Position? 2

Default value

Accept pipeline input? false

Accept wildcard characters? false



-ClusterId <String>

ClusterId for existing Databricks cluster. Does not need to be running. See Get-DatabricksClusters.



Required? true

Position? 3

Default value

Accept pipeline input? false

Accept wildcard characters? false



-LibraryType <String>

egg, jar, pypi, whl, cran, maven



Required? true

Position? 4

Default value

Accept pipeline input? false

Accept wildcard characters? false



-LibrarySettings <String>

Settings can by path to jar (starting dbfs), pypi name (optionally with repo), or egg



If jar, URI of the jar to be installed. DBFS and S3 URIs are supported. For example: { "jar":

"dbfs:/mnt/databricks/library.jar" } or { "jar": "s3://my-bucket/library.jar" }. If S3 is used, make sure the

cluster has read access on the library. You may need to launch the cluster with an IAM role to access the S3

URI.



If egg, URI of the egg to be installed. DBFS and S3 URIs are supported. For example: { "egg": "dbfs:/my/egg" }

or { "egg": "s3://my-bucket/egg" }. If S3 is used, make sure the cluster has read access on the library. You

may need to launch the cluster with an IAM role to access the S3 URI.



If whl, URI of the wheel or zipped wheels to be installed. DBFS and S3 URIs are supported. For example: {

"whl": "dbfs:/my/whl" } or { "whl": "s3://my-bucket/whl" }. If S3 is used, make sure the cluster has read

access on the library. You may need to launch the cluster with an IAM role to access the S3 URI. Also the

wheel file name needs to use the correct convention. If zipped wheels are to be installed, the file name

suffix should be .wheelhouse.zip.



If pypi, specification of a PyPI library to be installed. For example: { "package": "simplejson" }



If maven, specification of a Maven library to be installed. For example: { "coordinates":

"org.jsoup:jsoup:1.7.2" }



If cran, specification of a CRAN library to be installed.



Required? true

Position? 5

Default value

Accept pipeline input? false

Accept wildcard characters? false



<CommonParameters>

This cmdlet supports the common parameters: Verbose, Debug,

ErrorAction, ErrorVariable, WarningAction, WarningVariable,

OutBuffer, PipelineVariable, and OutVariable. For more information, see

about_CommonParameters (https:/go.microsoft.com/fwlink/?LinkID=113216).



INPUTS



OUTPUTS



NOTES





Author: Simon D'Morias / Data Thirst Ltd



-------------------------- EXAMPLE 1 --------------------------



PS C:\\>Remove-DatabricksLibrary -BearerToken $BearerToken -Region $Region -ClusterId 'Bob-1234'















RELATED LINKS