Exasol distributed ml
Skill exasol-labs/exasol-agent-skills/plugins/exasol/skills/exasol-distributed-ml
Exasol skills for AI agents. Optimized for Claude Code and OpenAI Codex π€
npx -y skills add exasol-labs/exasol-agent-skills --skill exasol-distributed-mlAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 10 stars10 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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, Lua execute script orchestration for iterative algorithms (k-means, SGD, Apriori), 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).
SKILL.md
4.3 KB, as published. Nobody here has run it
Exasol Distributed ML and HPC
Trigger when the user mentions: distributed ML, machine learning, train model, batch inference, prediction, feature engineering, hyperparameter, PyTorch, TensorFlow, scikit-learn, RAPIDS, GPU model, model deployment, distributed training, ensemble, anomaly detection, forecasting, clustering at scale, k-means, gradient descent, iterative algorithm, frequent itemset, association rules, market basket, Apriori, FP-Growth, data mining, SON algorithm, partial_fit, federated training, or any pattern where data is trained or scored inside Exasol.
Routing Algorithm
Choose the narrowest matching route. Load all routes that apply β they are designed to be read together.
Route 1 β Pipeline architecture, algorithms, and patterns
Trigger phrases: distributed training, end-to-end ML, feature engineering, batch inference, ensemble, k-means, gradient descent, frequent itemset, association rules, market basket, Apriori, FP-Growth, data mining, federated training, per-entity model, anomaly detection, forecasting, hyperparameter search, map-reduce
β Load: references/distributed-ml-patterns.md
Route 2 β Model storage, versioning, and lifecycle
Trigger phrases: save model, ONNX, joblib, pickle, model versioning, load model in UDF, update model, latest.json, model registry, model path, BucketFS model
β Load: references/model-lifecycle.md
Route 3 β GPU, CUDA, and RAPIDS
Trigger phrases: GPU UDF, CUDA SLC, PyTorch, TensorFlow, RAPIDS, cuDF, cuML, GPU acceleration, TorchScript, GPU cluster
β Load: references/gpu-acceleration.md
Route 4 β Performance, tuning, and memory
Trigger phrases: slow UDF, OOM, out of memory, memory_limit, data skew in ML, profile SET script, chunking, group size, partial_fit convergence, ctx.reset, multi-pass, epoch loop
β Load: references/ml-performance.md
Defer to Existing Skills
Do not re-explain these β activate the relevant skill instead:
- UDF API basics (ctx.emit, ctx.get_dataframe, SCALAR vs SET syntax, CREATE SCRIPT templates) β exasol-udfs
- SLC build/deploy (exaslct CLI, flavor selection, Dockerfile customization) β exasol-udfs
references/slc-reference.md - Lua execute script orchestration (query/pquery API, error handling) β exasol-udfs
references/lua-execute-scripts.md - BucketFS file operations (cp/ls/rm via exapump) β exasol-bucketfs
- DISTRIBUTE BY table design and query profiling β exasol-database
Key Principles
- Prefer
partial_fitalgorithms (SGD, MLP, MiniBatchKMeans) β stream chunks withctx.get_dataframe(num_rows=CHUNK_SIZE), loop epochs withctx.reset()for convergence - Avoid
ctx.get_dataframe(num_rows='all')β it materializes the entire group in memory - For algorithms without
partial_fit(RandomForest, GradientBoosting): use the map-reduce ensemble pattern (Section 6 of distributed-ml-patterns.md) rather than loading all data at once - Load models at module level (outside
run()), never insiderun() - Orchestrate iterative algorithms with Lua execute scripts (
query) rather than external drivers when possible - DISTRIBUTE BY on the training/inference key keeps related rows on the same node and eliminates shuffles