dfs_tool
It is a HDFS cli tool. You can use it to manage your HDFS file system.
It calls the WebHDFS API.
Configuration
You need to put a config file. By default, the config file is at ~/.dfs_tool/config.json, however you can change it's location by setting environment variable DFS_TOOL_CFG
The configuration looks like below:
{
"api_base_uri": "https://my_hdfs_cluster.com/gateway/ui/webhdfs/v1/",
"username": "superman",
"password": "mypassword",
"io_chunk_size": 16777216
}
In some case, server uses certificate to authenticate client, then you can config like below:
{
"api_base_uri": "https://my_hdfs_cluster.com/gateway/ui/webhdfs/v1/",
"auth_cert": "/Users/shizhong/.dfs_tool/sso_client.cer",
"auth_key" : "/Users/shizhong/.dfs_tool/sso_client.key",
"ca_cert" : "/Users/shizhong/.dfs_tool/CombinedDigicertCA.cer"
}
api_base_url: You need to put your WebHDFS endpoint hereusername: You need to specify your HDFS account usernamepassword: You need to specify your HDFS account passwordio_chunk_size: optional, if not set, the default value is 1048576. It is the chunk size for downloading data from HDFS or uploading data to HDFS, you may want to bump this value if your bandwidth is high
Command supported
dfs_tool ls [-R] <remote_path> -- list directory or file
dfs_tool download [-R] <remote_filename> <local_path> -- download file
dfs_tool cat <remote_filename> -- cat a file
dfs_tool mkdir <remote_dir_name> -- make a directory
dfs_tool rm [-RM] <remote_path> -- remove a file or directory
dfs_tool upload [-R] [-F] <local_filename> <remote_path> -- upload file
dfs_tool mv <source_location> <destination_location> -- move file or directory
Options
Some command support options, here are options:
-
-RIt means "recursive" -
-FIt means "force", in upload command, when-Fis specified, it will override the file already exist there. -
-MIn "rm" command, you can specify a pattern to match the files you want to delete, for example:
dfs_tool rm -M "/tmp/*.parquet"
Metadata
Release files for dfs-tool 0.0.10
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| dfs_tool-0.0.10.tar.gz | 6.2 kB | Without provenance | Details for dfs_tool-0.0.10.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dfs_tool-0.0.10-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for dfs_tool-0.0.10-py2.py3-none-any.whl |
Total release size: 14.4 kB
Release files / dfs_tool-0.0.10.tar.gz
| Download URL | dfs_tool-0.0.10.tar.gz |
|---|---|
| Size | 6.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5ee8bdbbe3346939d99fd9591668096524839a2e04f1af344cb8ebac3d66888a
|
|
BLAKE2b-256 checksum How to use checksums |
16133e0cc46beb07ea3f386b1f4f0d72738e04a80bd0e20deedc3647f5cb9dae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.36.1 CPython/3.6.8
|
Release files / dfs_tool-0.0.10-py2.py3-none-any.whl
| Download URL | dfs_tool-0.0.10-py2.py3-none-any.whl |
|---|---|
| Size | 8.1 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
8f131f4e944b7a0225d5e08282edb1a068efd25be741263f7725cb8def810b27
|
|
BLAKE2b-256 checksum How to use checksums |
872e1f6a7b71c8d266c68f8d2f8e50e653cbdb8b9e49394f4b907b731023d511
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.36.1 CPython/3.6.8
|
Security for dfs-tool 0.0.10
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.