Skip to content
cccskills
FreePublished on GitHub

exasol-itde

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.

The English summary is being prepared. Showing the original description.

Works withDocker

Run score Not tested

See how to install

Files included (6)

  • SKILL.md2.3 KB
  • references/itde-lifecycle.md3.1 KB
  • scripts/bring_itde_up.py1.0 KB
  • scripts/check_itde_status.py996 B
  • scripts/restart_itde.py789 B
  • scripts/take_itde_down.py750 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Exasol ITDE Skill

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.

Routing Algorithm

  1. Start local Docker DB

    • Trigger phrases: bring_itde_up, start local exasol, docker-db
    • Load: references/itde-lifecycle.md
    • Use scripts from: scripts/
  2. Check status / restart / tear down

    • Trigger phrases: get_itde_status, restart_itde, take_itde_down, container status
    • Load: references/itde-lifecycle.md
    • Use scripts from: scripts/
  3. Config not present yet

    • Activate exasol-notebook-connector-config

Validation

Use the lifecycle scripts to validate the stored ITDE setup:

  • run scripts/check_itde_status.py after setup changes
  • after bring_itde_up, expect ItdeContainerStatus.READY
  • if the next step is the shared exasol-notebook-connector-config validation flow, save storage_backend=onprem first because bring_itde_up(...) does not populate that key itself
  • set db_schema yourself before handing off to schema-dependent workflows such as SQLAlchemy, Ibis, TE, or TXAIE validation
  • after teardown, expect ABSENT or a clean no-container state

Expected failure mode:

  • scripts/restart_itde.py should raise a runtime error if the Docker-DB container does not exist yet
  • shared setup validation can fail with missing storage_backend or db_schema even when ITDE itself is healthy, because those keys are not written by bring_itde_up(...)
  • if status checks fail because the store is missing, switch back to exasol-notebook-connector-config

Notes

  • ITDE is the easiest local development database path for notebook-connector.
  • 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.
  • After ITDE is ready, other notebook-connector connection APIs can be used without manual DB/BucketFS entry.

Reviews

No reviews yet. Tell others what you thought.

Comments

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.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

exasol

Free

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-labs/exasol-agent-skills10Updated Oct 14, 2026

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-labs/exasol-agent-skills10Updated Oct 14, 2026

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.

exasol-labs/exasol-agent-skills10Updated Oct 14, 2026

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.

exasol-labs/exasol-agent-skills10Updated Oct 14, 2026

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.

exasol-labs/exasol-agent-skills10Updated Oct 14, 2026

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.

exasol-labs/exasol-agent-skills10Updated Oct 14, 2026

See all skills by exasol-labs

Report a problem with this skill