メニュー
Use Exasol EXPORT SQL plus exapump local file export workflows for moving data out of Exasol. Covers native CSV/FBV export, local CSV/Parquet exports with exapump, connection objects, reject limits, and export credential patterns.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Exasol database interaction via exapump CLI and Exasol SQL. Covers SQL queries, schema inspection, table design, query profiling, analytics, and Exasol-specific SQL behavior outside exasol-import and exasol-export.
Catalog and routing guide for Exasol tools, extensions, connectors, integrations, and architecture patterns. Use when users ask how to extend, customize, deploy, load, explore, enrich, surface, scale, automate, govern, migrate, or integrate Exasol, including Exasol Labs tools, AI/ML, UDFs, lakehouse, SAP, Databricks, agentic workflows, or product/version status.
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.
Build, install, validate, and debug custom Exasol virtual schema adapters. Covers source-specific JDBC dialect implementation with virtual-schema-common-jdbc, custom document-file adapter code boundaries, JAR packaging, BucketFS deployment, adapter script setup, EXPLAIN VIRTUAL validation, and adapter-side remote debugging workflows.
Use Exasol document-file virtual schemas for federated read-only access to object and file storage. Covers document-file adapter family selection, CREATE VIRTUAL SCHEMA usage, refresh workflows, and query-side troubleshooting.
Use Exasol JDBC-based virtual schemas for federated read-only access to external databases. Covers database-source adapter selection, CREATE VIRTUAL SCHEMA, EXPLAIN VIRTUAL, metadata refresh, and query-side troubleshooting.
| name | exasol-export |
| description | Use Exasol EXPORT SQL plus exapump local file export workflows for moving data out of Exasol. Covers native CSV/FBV export, local CSV/Parquet exports with exapump, connection objects, reject limits, and export credential patterns. |
This skill covers only workflows that move data out of Exasol.
Ensure a working exapump profile before giving terminal workflows that use
exapump export:
exapump sql --profile <name> "SELECT 1"; always place --profile after the subcommand.exapump sql "SELECT 1".exapump profile list.exapump sql --profile <name> "SELECT 1"; keep --profile after the subcommand.--profile <name> after the subcommand on subsequent exapump commands, such as exapump export --profile <name> --table <schema.table> --output <file> --format <format>.exapump profile add default and retry.Trigger when the user mentions EXPORT, EXPORT INTO, export table, export local file, exapump export, export CSV, export Parquet, export to S3, export to Azure Blob, export to GCS, export to FTP, export to SFTP, export to HTTP, export to HTTPS, REJECT LIMIT with export intent, or CREATE CONNECTION together with export target setup intent.
Local files on the user machine
export local file, into local, to local, exapump exportreferences/export.mdRemote or cloud files reachable by Exasol
EXPORT, EXPORT INTO, S3, Azure Blob, GCS, FTP, SFTP, HTTP, HTTPS, REJECT LIMIT, CREATE CONNECTION with export target setup intentreferences/export.mdConnection-object export setup
CREATE CONNECTION with export target setup intent, ALTER CONNECTION, temporary credentials, SESSION TOKENreferences/export.mdScript-based export target
EXPORT INTO SCRIPT, export script, custom export scriptreferences/export.mdIMPORT, local upload workflows, Parquet import, reject handling, and staging-based loading into Exasol.EXPORT or exapump export.