Exasol BucketFS file system management via the `exapump bucketfs` CLI. Covers listing, uploading, downloading, and deleting files and directories in BucketFS, the `bfsdefault` service and other bucket services, bucket structure, `bfs_*` profile settings, the `/buckets/<service>/<bucket>/<path>` UDF path, and staging JARs, models, and Script Language Containers for UDFs.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
BucketFS is Exasol's synchronous distributed file system: whatever is written to
a bucket is replicated to every cluster node and mounted read-only inside UDFs
at /buckets/<service>/<bucket>/<path>. Replication takes time, and recognised
archives are extracted on top of it, so a fresh upload becomes usable only once
synchronisation finishes. This skill covers moving files in and out of BucketFS
and referencing them from scripts.
Choose the narrowest matching route. If several apply, load all matching references before answering.
Run a BucketFS operation — list, upload, download, delete, or configure the connection
exapump bucketfs, ls, cp, rm, upload, download, delete, --bfs-host, --bfs-bucket, bfs_write_password, config.toml, exapump profile addreferences/exapump-bucketfs-cli.mdStage a file for a UDF or SLC — JARs, pickled models, containers, and the SQL that points at them
upload jar, %jar, upload model, load model in UDF, upload SLC, activate containerreferences/bucketfs-udf-usage.mdUnderstand BucketFS itself — services, buckets, path forms, replication, durability
what is BucketFS, bfsdefault, service, bucket structure, replication, backup, atomic write, size limitreferences/bucketfs-concepts.mdAn upload for a UDF usually needs routes 1 and 2 together: the command form comes from the CLI reference, the path spelling in the SQL from the usage reference.
Ensure a working exapump profile — BucketFS uses the profile's bfs_*
fields — before running any command:
exapump bucketfs ls --profile <name>; always place --profile after the subcommand. Otherwise test the default profile with exapump bucketfs ls.--profile <name> after the subcommand on every later command, such as exapump bucketfs cp --profile <name> <local-file> <bucket-path>.exapump profile list to see which profiles exist.exapump profile show <name> — it masks credentials — to confirm the required fields are set. Never read, cat, or print ~/.exapump/config.toml; it stores credentials in clear text. If a credential value does appear in any command output, do not repeat it in the conversation.exapump profile add <name> (omit --password and exapump prompts on a hidden line) or exapump profile init, then retry step 1. Never ask the user to paste a password into the conversation, and never pass one as a command-line argument.rm, show the exact bucket, path, and profile, then obtain explicit
confirmation. BucketFS is not part of database backups, so a deletion is not
recoverable from a database restore.cp that would overwrite an existing BucketFS or local file, inspect
the target and obtain confirmation.exapump profile show <name>, never by reading ~/.exapump/config.toml.まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Top-level router for Exasol work. Use for any Exasol database, exapump, SQL, BucketFS, extension, integration, UDF, Script Language Container, or Exasol Personal setup task, then route to the narrowest specialized Exasol skill.
日本語の概要は準備中です。原文の説明を表示しています。
Use Exasol Cloud Storage Extension workflows for moving structured object-storage files through extension UDFs. Covers setup prerequisites, the fixed `CLOUD_STORAGE_EXTENSION.IMPORT_PATH` and `CLOUD_STORAGE_EXTENSION.EXPORT_PATH` entrypoints used with `FROM SCRIPT` and `INTO SCRIPT`, Parquet, Avro, ORC, and Delta files on S3, Google Cloud Storage, Azure Blob Storage, Azure Data Lake, HDFS, and Alluxio, connection-object credential patterns, and routing away from native IMPORT or EXPORT when the extension path is the right fit.
日本語の概要は準備中です。原文の説明を表示しています。
Exasol database interaction via the exapump CLI and Exasol SQL. Covers SQL queries and DML/DDL such as `SELECT`, `INSERT`, `UPDATE`, `DELETE`, `MERGE`, `CREATE TABLE`, `ALTER TABLE`, and `DROP TABLE`, `CREATE CONNECTION` connection objects without import or export intent, schema inspection, table design, `exapump sql` and `exapump profile`, query profiling, analytics, and Exasol-specific SQL behavior outside exasol-import and exasol-export.
日本語の概要は準備中です。原文の説明を表示しています。
Distributed machine learning, data mining, and iterative HPC with Exasol. Covers end-to-end ML pipelines (DISTRIBUTE BY + SET scripts + BucketFS), per-entity federated training with partial_fit and ctx.reset(), batch inference, map-reduce ensemble training, distributed ensemble and SON algorithm for frequent itemset mining (Apriori, FP-Growth, association rules, market-basket analysis), Lua execute script orchestration for iterative algorithms (k-means, SGD, gradient descent), scikit-learn model training, parallel hyperparameter search, per-entity forecasting, anomaly detection, model lifecycle in BucketFS (pickle/joblib/ONNX versioning), GPU acceleration via CUDA SLCs (PyTorch/TensorFlow/RAPIDS), and ML-specific performance tuning (skew, OOM, multi-pass chunking).
日本語の概要は準備中です。原文の説明を表示しています。
Use Exasol document-file virtual schemas for federated read-only access to object and file storage — S3, Google Cloud Storage, Azure Blob Storage, and Azure Data Lake Storage Gen2 document files. Covers document-file adapter family selection, the EDML `MAPPING` definition, `CREATE VIRTUAL SCHEMA` usage, refresh workflows, and query-side troubleshooting.
日本語の概要は準備中です。原文の説明を表示しています。
Use Exasol `EXPORT` and `EXPORT INTO` SQL plus `exapump export` local file workflows for moving data out of Exasol. Covers native CSV/FBV export, local CSV/Parquet exports with exapump, `CREATE CONNECTION` connection objects for export, FTP, SFTP, HTTP, HTTPS, and cloud targets on S3, Azure Blob Storage, and Google Cloud Storage (GCS), reject limits, and export credential patterns.
日本語の概要は準備中です。原文の説明を表示しています。