メニュー
Use notebook-connector's itde_manager to run a local Docker-based Exasol database. Covers bring_itde_up, get_itde_status, restart_itde, take_itde_down, and how ITDE populates notebook-connector configuration automatically.
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-itde |
| description | Use notebook-connector's itde_manager to run a local Docker-based Exasol database. Covers bring_itde_up, get_itde_status, restart_itde, take_itde_down, and how ITDE populates notebook-connector configuration automatically. |
Trigger when the user mentions ITDE, docker-db, local Exasol Docker database, bring_itde_up, restart_itde, take_itde_down, or local notebook-connector database setup.
Start local Docker DB
bring_itde_up, start local exasol, docker-dbreferences/itde-lifecycle.mdscripts/Check status / restart / tear down
get_itde_status, restart_itde, take_itde_down, container statusreferences/itde-lifecycle.mdscripts/Config not present yet
Use the lifecycle scripts to validate the stored ITDE setup:
scripts/check_itde_status.py after setup changesbring_itde_up, expect ItdeContainerStatus.READYstorage_backend=onprem first because bring_itde_up(...) does not populate that key itselfdb_schema yourself before handing off to schema-dependent workflows such as SQLAlchemy, Ibis, TE, or TXAIE validationABSENT or a clean no-container stateExpected failure mode:
scripts/restart_itde.py should raise a runtime error if the Docker-DB container does not exist yetstorage_backend or db_schema even when ITDE itself is healthy, because those keys are not written by bring_itde_up(...)bring_itde_up populates the secure config store with the generated DB and BucketFS connection details automatically.bring_itde_up does not populate storage_backend or db_schema.