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.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Trigger when the user mentions Cloud Storage Extension, FROM SCRIPT CLOUD_STORAGE_EXTENSION, INTO SCRIPT CLOUD_STORAGE_EXTENSION, CLOUD_STORAGE_EXTENSION.IMPORT_PATH, CLOUD_STORAGE_EXTENSION.EXPORT_PATH, Avro/ORC/Delta object-storage import, extension-based object-storage loading, extension-based Parquet reader, Avro through Cloud Storage Extension, ORC through Cloud Storage Extension, Delta through Cloud Storage Extension, extension-based Parquet export, or extension-based file reader.
Cloud Storage Extension, FROM SCRIPT CLOUD_STORAGE_EXTENSION, INTO SCRIPT CLOUD_STORAGE_EXTENSION, CLOUD_STORAGE_EXTENSION.IMPORT_PATH, CLOUD_STORAGE_EXTENSION.EXPORT_PATH, Avro from object storage, ORC from object storage, Delta from object storage, ORC from S3, Avro from S3, Delta from S3, extension-based object-storage loading, extension-based Parquet reader, ORC through Cloud Storage Extension, Avro through Cloud Storage Extension, Delta through Cloud Storage Extension, extension-based Parquet exportreferences/cloud-storage-extension.mdIMPORT or EXPORT.exapump export.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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).
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.