Repository navigation
Releases
3.1.2
Minitrino Release Notes: 3.1.2
Release Overview
Minitrino 3.1.2 is a maintenance release that updates dependencies and fixes
the release smoke test, which was reporting false passes.
Key improvements:
- Updated
clickto 8.5.0 anddockerto 7.2.0 - Updated GitHub Actions to their latest major versions
- Fixed the release smoke test so provisioning failures are detected, and fixed
Docker Compose and Buildx setup on macOS runners
Table of Contents:
CLI Changes and Additions
Dependency Updates
click:8.3.3→8.5.0docker:7.1.0→7.2.0
Library Changes and Additions
Reduced Memory Usage of cache-service Example Materialized View
The example materialized view created by the cache-service module selected
500 rows per branch of a UNION ALL while partitioning by orderdate, creating
a partition (and ORC writer) for nearly every row. Its refresh used roughly 80%
of the default per-node query memory limit and could exceed it, causing the
refresh to fail. The view now selects 50 rows per branch, reducing peak refresh
memory from ~480 MB to ~57 MB.
Other
CI/CD: Smoke Test False Passes
The provision step of the release smoke test captured the exit code of tee
rather than minitrino provision, so it always passed. This masked a real
failure on macOS runners, where Homebrew's docker formula does not include the
Docker Compose v2 or Buildx plugins.
The fix:
- The provision step now uses
PIPESTATUSto capture the correct exit code - The macOS runner installs and registers the
docker-composeand
docker-buildxplugins - A new step verifies Docker,
docker compose, anddocker buildxbefore
provisioning - Colima startup on macOS is bounded to 8 minutes per attempt and retried once
from a clean VM, and the job has a 35-minute timeout, so a hung runner fails
quickly instead of blocking the release gate
CI/CD: Reusable Smoke Test Workflow
The smoke test has moved from release.yaml into a reusable smoke-test.yaml
workflow. It still gates the release, and can now also be run:
- Manually via
workflow_dispatchagainst any published version - Automatically on pull requests that modify
smoke-test.yaml, against the
latest published version
CI/CD: Build Test Images When Fallback Images Are Missing
When a PR does not change image-related files, CI skips building test images
and pulls latest-trino and latest-starburst from GHCR instead. No workflow
publishes those images, so they were missing and every test job failed during
setup. Change detection now builds the test images whenever those fallback
images cannot be resolved.
CI/CD: macOS Runner Update
The macOS smoke test now runs on macos-15-intel. The previous macos-13
runner image was retired by GitHub, which caused the job to queue indefinitely.
CI/CD: GitHub Actions Updates
actions/checkout:v6→v7actions/setup-python:v6→v7actions/setup-java:v4→v5actions/cache:v4→v6
0.0.0
Used as a placeholder to give test builds access to the PR branch's module library.
3.1.1
Minitrino Release Notes: 3.1.1
Release Overview
Minitrino 3.1.1 is a patch release that restores the minio module after the
upstream minio/minio and minio/mc images were removed from Docker Hub.
Key improvements:
- Switched the
miniomodule to the community-maintainedpgsty/minioand
pgsty/mcimages
Table of Contents:
Library Changes and Additions
Bug Fix: MinIO Images Removed from Docker Hub
MinIO has stopped distributing community images, and both minio/minio and
minio/mc are no longer available on Docker Hub. As a result, provisioning the
minio module (and every module that depends on it, including hive,
iceberg, iceberg-hms, delta-lake, spooling-protocol, and
results-cache) failed with an image pull error.
The fix:
- The
minioservice now usespgsty/minio, and theminio-clientservice
now usespgsty/mc. These are drop-in, multi-arch (amd64/arm64) forks of the
upstream images. - Updated version pins in
minitrino.env:MINIO_VER:RELEASE.2025-05-24T17-08-30Z→RELEASE.2026-08-04T00-00-00ZMINIO_MC_VER:RELEASE.2025-05-21T01-59-54Z→
RELEASE.2026-09-16T00-00-00Z
Users who override MINIO_VER or MINIO_MC_VER must use a tag published under
the pgsty/minio and pgsty/mc repositories.
Other
Bug Fix: Makefile Targets Reporting Success on Failure
The pre-commit, unit-tests, integration-tests, lib-tests, and
coverage Make targets pipe their output through tee, which masked the exit
code of the underlying command. These targets reported success even when the
command failed (including when ./venv did not exist).
- Recipes now run under
bash -o pipefail, so failures are propagated - Colored status messages use
printffor portability across shells PYTHONcan be overridden (e.g.,make pre-commit PYTHON=/path/to/python)
This only affects local development workflows; CI does not use these targets.
Bug Fix: Docs Switcher Hook Omitting Trailing Newline
The update-switcher-json pre-commit hook wrote docs/_static/switcher.json
without a trailing newline, causing end-of-file-fixer to reject the first
commit on every new release branch. The hook now writes a trailing newline.
3.1.0
Minitrino Release Notes: 3.1.0
Release Overview
Minitrino 3.1.0 is a feature release that adds local source-code builds, a
safer and more interactive library upgrade experience, and a data-driven image
build pipeline. It also bumps the default cluster version to 479 (Java 25) and
overhauls the CI/test infrastructure.
Key improvements:
- New
provision --source-codeoption to build images from a local Trino or
Starburst source repository instead of a published tarball - Automatic library version-sync prompts with non-destructive, backup-based
installs (previous library is retained, not overwritten) - New global
--yes/-yflag (andMINITRINO_ASSUME_YES) to auto-accept
prompts for CI and scripted workflows - Default cluster version bumped from 476 to 479, with a data-driven Java
version matrix (Java 25) - Restructured, data-driven image build pipeline (declarative plugin removelist
and Java matrix) - Automatic resolution of the latest Starburst patch release
- Internal package layout flattened from
src/cli/minitrinotosrc/minitrino
Table of Contents:
CLI Changes and Additions
Build Images From Local Source Code
Added a -s / --source-code option to minitrino provision. Instead of
downloading a published Trino/Starburst tarball, Minitrino can now build the
cluster image directly from local Maven build output:
minitrino provision --source-code /path/to/trinoThe path may be either a repository root (Minitrino locates the Maven build
output under core/trino-server/target/ or
core/starburst-enterprise/target/) or a direct distribution directory. The
distribution type and version are auto-detected from the build output; if you
also pass --image, Minitrino validates that it matches the detected
distribution and errors on a mismatch. This is intended for developers testing
unreleased or locally patched builds of Trino/Starburst.
When --source-code is used, KEEP_PLUGINS defaults to ALL so that locally
built plugins are never stripped from the image. Set KEEP_PLUGINS explicitly
(including to an empty value) to apply the standard plugin removelist.
Interactive Library Version Syncing
When the CLI and library versions don't match, Minitrino now prompts to sync
automatically rather than only printing a warning:
CLI version 3.1.0 does not match library version 3.0.0. Sync library to 3.1.0? [Y/N]
- If you accept, the library is replaced with the matching version.
- If you decline, the prompt is suppressed for 24 hours before asking again.
- If no library is installed at all, Minitrino prompts to install one; declining
raises an error since most commands require a library.
Safer, Non-Destructive Library Installs
minitrino lib-install (and the automatic sync above) no longer destructively
overwrites the existing library. The current library is moved aside to
~/.minitrino/lib.bak.<UTC timestamp> before the new one is installed:
- If the download or extraction fails, the previous library is automatically
restored from the backup. - After a successful install, old backups are pruned, retaining the two most
recent.
This replaces the previous behavior, which deleted all modules and snapshots in
place with no recovery path.
--yes / -y Global Flag
Added a global -y / --yes flag that assumes "yes" for all interactive
prompts, equivalent to setting MINITRINO_ASSUME_YES=1. This is useful for CI
pipelines and scripted workflows where the new sync/install prompts would
otherwise block.
Library Changes and Additions
Default Cluster Version Bumped to 479
The default CLUSTER_VER is now 479 (previously 476), which runs on Java 25.
Data-Driven Image Build Pipeline
The image build pipeline under src/lib/image/ was restructured and made
data-driven:
- Java version matrix (
data/java-matrix.json): the correct JDK is now
selected from a declarative Trino-version-to-Java mapping (Java 23 for
464–467, Java 24 for 468–475, Java 25 for 476+). - Declarative plugin removelist (
data/plugin-removelist.txt): plugins to
strip from the image are now listed in a data file rather than hardcoded in
the pruning script.KEEP_PLUGINScontinues to override removals (and
KEEP_PLUGINS=ALLkeeps everything). - The
src/lib/image/src/nesting was flattened tosrc/lib/image/, and the
tarball downloader was renamed (downloader.py→download_tarball.py).
Dockerfile Support for Local Source Builds
The Dockerfile now supports two build sources selected via the DIST_SOURCE
build arg: download (fetch a published tarball, the default) or local (stage
a locally built distribution). This is what powers provision --source-code.
Automatic Starburst Version Resolution
Added a utility that resolves the latest Starburst patch release for a given LTS
base version by querying the Starburst S3 bucket (e.g. 479 → 479-e.8), with
a safe fallback when the lookup fails. This is used by version validation and CI
so tests track the latest available patch automatically.
Module Fixes
- cache-service: heap size raised to 2G.
- mysql-event-listener: startup now gated on MySQL health to avoid race
conditions. - worker provisioning: fixed a
put_archiverace by staging/etcbefore
the container starts.
Other
CI/CD
- Rewrote the main CI workflow and added a
collect-failure-diagnostics
composite action to capture logs and state on test failures. - Added an
update-version-filesworkflow that automatically bumps
src/lib/version,pyproject.toml, andreadme.mdwhen a new
MAJOR.MINOR.PATCHrelease branch is pushed, replacing the previous
sync_version_files.pypre-commit script. - Removed the now-unused
pull-test-imageandwait-for-test-releaseactions.
Testing
- Migrated the library test suite to pytest and added shared fixtures.
- Added a test watchdog to detect and recover from hung test runs.
- Reorganized the unit test tree to mirror the flattened package layout.
Internal Package Restructure
The CLI package was moved from src/cli/minitrino to src/minitrino, and the
minitrino.core.* subpackage was flattened into minitrino.* (e.g.
minitrino.core.context → minitrino.context). This affects only direct
imports of Minitrino internals; the minitrino CLI entry point is unchanged.
Dependencies
clickbumped from 8.3.1 to 8.3.3.
3.0.3
Minitrino Release Notes: 3.0.3
Release Overview
Minitrino 3.0.3 is a patch release that fixes a critical bug preventing the CLI
from working when installed from PyPI without a pre-existing library, and adds
automated smoke testing to catch similar issues in future releases.
Key improvements:
- Fixed
lib-installandconfigcommands failing when no library is installed - Added minimal initialization mode for commands that don't require a library
- Added cross-platform PyPI smoke test workflow (Ubuntu + macOS)
Table of Contents:
CLI Changes and Additions
Bug Fix: Commands Failing Without Library Installed
Fixed a critical bug where minitrino lib-install and minitrino config
commands would fail with "This operation requires a library to be installed"
error when run on a fresh installation from PyPI.
Root cause: During context initialization, the _compare_versions() method
was called unconditionally, which accessed lib_dir, which raised an error if
no library was found. This created a chicken-and-egg problem where users
couldn't install the library because the command to install it required a
library to already exist.
The fix:
- Renamed
_compare_versions()to_try_compare_versions()and wrapped it in
try/except to gracefully handle missing libraries - Added
minimal=Trueparameter toinitialize()that skips library-dependent
operations (module loading, cluster setup, Docker client initialization) - Updated
lib-installandconfigcommands to use minimal initialization
This bug only affected users installing from PyPI into an isolated environment.
Users running from the repository or with an existing library were not affected
because the fallback logic found src/lib/ in the repo tree.
Other
CI/CD: Integrated Smoke Test as Release Gate
Restructured the release workflow to use the smoke test as a gate before
creating the GitHub release. The new flow is:
- PyPI Publish - Package is built and uploaded to PyPI
- Smoke Test - Cross-platform tests verify the PyPI package works
- GitHub Release - Only created if smoke test passes
This ensures that if the smoke test fails, the PyPI package exists but no
official GitHub release is created, preventing broken releases from being
announced.
Smoke test features:
- Truly isolated testing: Does NOT checkout the repository, simulating an
end-user installation experience - Cross-platform coverage: Runs on both Ubuntu 22.04 and macOS 13
- Comprehensive command testing:
minitrino config --reset(without library - validates the bug fix)minitrino lib-install(without library - validates the bug fix)minitrino modules(with library)minitrino provisionwith 30-second timeout (validates Docker integration)
CI/CD: CLI Integration Test Sharding
Split the CLI integration tests into 4 parallel jobs to reduce CI bottleneck:
| Job | Tests | Description |
|---|---|---|
| Provision | 10 | test_cmd_provision.py |
| Snapshot | 8 | test_cmd_snapshot.py |
| Remove | 7 | test_cmd_remove.py |
| Other | 12 | Remaining 9 test files |
Previously, "Other" ran 37 tests while "Provision" ran only 10, causing a
significant bottleneck. The new distribution (10/8/7/12) provides better
parallelization.
Closes #144.
3.0.2
Minitrino Release Notes: 3.0.2
Release Overview
Minitrino 3.0.2 is a patch release that fixes critical documentation issues and
improves the release workflow infrastructure.
Key improvements:
- Fixed documentation version selector to display actual version instead of
always showing "master" - Fixed version sync script to prevent corruption of ruff configuration
- Blacklisted broken 3.0.0 documentation build
- Enhanced pre-commit hooks to auto-stage generated documentation files
- Updated release workflow to ensure correct branch checkout
Table of Contents:
CLI Changes and Additions
No CLI changes in this release.
Other
Documentation Fixes
-
Version selector display fix: The ReadTheDocs version selector dropdown
now correctly displays the actual documentation version (e.g., "3.0.2",
"3.0.1") instead of always showing "master". This was caused by a hardcoded
github_versionvalue indocs/conf.pythat has been updated to use the
dynamicreleasevariable. -
Blacklisted 3.0.0 documentation: Version 3.0.0 documentation cannot be
built due to a typo in.readthedocs.yaml(extra_requiresvs
extra_requirements). Added a blacklist system to the version switcher
script to prevent 3.0.0 from appearing in documentation version selectors.
Users should refer to 3.0.1+ documentation.
Build & Release Infrastructure
-
Version sync script fix: Fixed the
sync_version_files.pypre-commit
hook to only update the version field in the[project]section of
pyproject.toml, preventing it from incorrectly modifying ruff's
target-versionconfiguration (which expects Python versions likepy310,
not project versions). -
Auto-stage documentation changes: The
update_switcher_json.py
pre-commit hook now automatically stagesdocs/_static/switcher.jsonafter
modifying it, eliminating the need for manual staging and preventing
commit failures. -
Release workflow improvements: Updated the GitHub Actions release
workflow to explicitly checkout from themasterbranch when creating
releases, ensuring releases are always created from the correct source.
Repository Configuration
- Auto-delete merged branches: Enabled GitHub's auto-delete branch setting
to automatically clean up release branches after they're merged. This
prevents ReadTheDocs slug conflicts between Git branches and tags with the
same name.
Dependency Updates
- click: Bumped from 8.1.8 to 8.3.1
- actions/checkout: Bumped from v5 to v6 in GitHub Actions workflows
3.0.1
Minitrino Release Notes: 3.0.1
Release Overview
Minitrino 3.0.1 is a patch release that improves configuration parsing, modernizes
CI/CD infrastructure, and establishes comprehensive code quality standards.
Key improvements:
- Fixed critical config parsing bug with quoted values
- Modernized GitHub Actions with intelligent change detection and modular design
- Migrated to Ruff for faster linting and formatting
- Applied 238+ code quality fixes across entire codebase
- Enhanced pre-commit hooks with 10+ new quality checks
Table of Contents:
CLI Changes and Additions
Configuration File Improvements
-
Quote stripping in config files: Configuration values in
minitrino.cfg
can now include single or double quotes without causing parse errors. Quotes
are automatically stripped when values are loaded, making config files more
flexible and editor-friendly.Example:
[config] LIB_PATH="/home/user/minitrino-lib" CLUSTER_NAME='my-cluster' IMAGE=trino
All three formats above now work correctly, with quotes automatically removed
during parsing. Previously, quoted values would fail to parse or include the
quotes in the actual value.
Other
CI/CD Infrastructure
-
Modernized GitHub Actions workflows: Replaced monolithic CI workflows with
modular composite actions for better maintainability and reusability. -
Intelligent change detection: Image builds now run conditionally based on file
changes, significantly reducing CI time and resource usage. When image files
haven't changed, tests use existing images from the main branch. -
Reusable composite actions: Created 4 new composite actions to eliminate
duplication across workflows:prepare-test-matrix- Dynamic test matrix generation for parallel executionsetup-docker-build- Docker build environment with GHCR authenticationsetup-image-pull- Conditional image pulling with fallback logicsetup-test-environment- Unified test environment setup
-
Improved test execution: Enhanced parallel test execution with dynamic matrix
generation for both Trino and Starburst test variants. -
Dependabot automation: Added comprehensive Dependabot configuration for
automated dependency updates across Python packages, GitHub Actions, and
Dockerfiles with intelligent grouping and security-critical dependency isolation.
Code Quality & Tooling
-
Modernized pre-commit tooling: Replaced Black, flake8, and isort with Ruff
for faster, more comprehensive Python linting and formatting. Ruff provides all
the functionality of the previous tools in a single, high-performance package. -
Enhanced pre-commit hooks: Added new universal linting and quality checks:
docformatter- Automatic docstring formattingmdformat- Markdown formatting (replacing prettier)typos- Spell checking for documentation fileshadolint- Dockerfile lintingactionlint- GitHub Actions workflow validation- General file checks (check-yaml, check-toml, check-json, check-merge-conflict, trailing-whitespace, end-of-file-fixer, check-added-large-files)
-
Security & code quality analysis (informational): Added non-blocking hooks:
bandit- Python security lintervulture- Dead code detectiondeptry- Dependency usage validation
-
Test validation hook: Added
validate-pytest-collectionto ensure all tests
can be collected without errors before commit. -
Updated hook versions:
- shellcheck: v0.10.0 → v0.11.0
- mypy: v1.16.1 → v1.18.1
-
Organized configuration: Pre-commit config now uses clear section headers
for better maintainability. -
Applied comprehensive linting fixes: Fixed 238+ code quality issues
identified by new tooling including improved exception handling with proper
chaining (15+ locations), modernized type annotations, simplified context
managers, removed dead code, and standardized formatting across all modules.
All Python files now comply with strict linting standards.
Documentation
- ReadTheDocs configuration fix: Updated
.readthedocs.yamlto use
extra_requirementsinstead of deprecatedextrasfield, resolving
documentation build failures.
3.0.0
Minitrino Release Notes: 3.0.0
Release Overview
Minitrino 3.0.0 represents a major evolution of the project, transforming it
from a Starburst-only tool into a universal local cluster management solution
for the entire Trino ecosystem. This release delivers game-changing capabilities
including native Trino support, multi-cluster orchestration, and a
completely modernized architecture built for production-grade developer
experiences.
Highlights:
- 🎉 Trino Support: Full compatibility with Trino 443+ alongside Starburst
443-e+ - 🚀 Multi-Cluster: Deploy and manage multiple isolated clusters
simultaneously - 🏗️ Modernized Architecture: Complete overhaul with Python 3.10+,
pyproject.toml, and enhanced modularity - 📊 Production Logging: Advanced logging system with spinners, buffering,
and colored output - 📚 Comprehensive Docs: Full Sphinx documentation site with API references
and user guides - 🧪 Testing Overhaul: Enhanced test infrastructure with better coverage and
organization
By the Numbers:
- ~300 commits since release 2.2.4
- 500+ files changed
- 28k+ lines added
- 8k+ lines removed
- 26 new core Python modules
- 37 modules across admin, catalog, and security categories
Table of Contents:
Breaking Changes & Upgrade Guide
section carefully before upgrading.
1. Trino Support & Configuration Changes
Minitrino now supports both Trino and Starburst distributions. This requires
configuration updates:
Environment Variable Changes:
STARBURST_VER→CLUSTER_VER(version of Trino/Starburst)- New
IMAGEvariable required: Set totrinoorstarburst(maps to
CLUSTER_DISTinternally) ETC = "/etc/starburst"→ETC = "/etc/${CLUSTER_DIST}"(now dynamic
based on distribution)
Action Required: Update your ~/.minitrino/minitrino.cfg file with:
CLUSTER_VER=476 # or your preferred version
IMAGE=trino # or 'starburst'2. Python Version Requirement
Minimum Python version increased from 3.8 to 3.10.
Action Required: Upgrade Python if needed: python --version
3. Project Structure Refactor (#125)
Major reorganization of the codebase:
- setup.py → pyproject.toml: Modern Python packaging standards
- Command files renamed:
cmd_*.py→*.py(e.g.,cmd_provision.py→
provision.py) - Core reorganized: New subdirectories
core/cluster/,core/docker/,
core/logging/,core/exec/
Action Required: If you import Minitrino modules directly, update import
paths.
4. Bootstrap & Entrypoint Changes
The container bootstrap lifecycle has been rewritten with new before/after
hooks.
Action Required: Custom modules with bootstrap scripts must be updated to
use the new API. See the module development documentation.
5. Docker Labels Changed
- Previous:
com.starburst.tests=minitrino - Now:
org.minitrino.root=trueandorg.minitrino.module
Action Required: Update any scripts that filter by Docker labels.
6. Container Image Naming
Container image naming has changed to support both distributions:
- Previous:
minitrino/trino:${STARBURST_VER} - Now:
minitrino/cluster:${CLUSTER_VER}-${CLUSTER_DIST}
Action Required: Update any scripts or configurations that reference the old image name.
7. CLI Option Changes
--docker-nativeflag removed; image builds now happen automatically when
needed- Build is triggered automatically when: (1) the image doesn't exist, or (2)
the image source has changed - Configuration file format updated
Action Required: Remove --docker-native from any scripts (no replacement
needed).
Upgrade Steps
- Upgrade Python to 3.10 or higher if needed
- Update configuration file (
~/.minitrino/minitrino.cfg) with new
variables - Install 3.0.0:
pip install --upgrade minitrino - Install library:
minitrino lib-install(auto-prompted if needed) - Test with new syntax:
minitrino -c test provisionto verify - Update custom modules if you have any
CLI Changes and Additions
New Commands
restart: Restart cluster containers without full reprovisioning- Enhanced
resources: View cluster resources with filters (--container,
--volume,--image,--network) - Enhanced
exec: Improved container command execution with interactive
shell support (-iflag), container selection, and user specification
Multi-Cluster Support
--cluster/-cflag: Deploy and manage multiple isolated clusters
simultaneously- Shared networking: Cross-cluster communication via shared cluster networks
- Independent lifecycles: Each cluster operates independently with its own
resources - Example:
minitrino -c prod provision --modules hive,iceberg+minitrino -c dev provision --modules postgres
Library Management
- LibraryManager class: Automated library installation and version
management (#103) - Auto-install/upgrade: Automatically installs library if missing or prompts
for upgrade on version mismatch --list-releases: View available Minitrino library releases- Smart detection: CLI detects library/version mismatches and guides users
Logging System Overhaul
- Complete rewrite using Python's native logging facility
- Colored output: Terminal-aware formatting with severity-based colors
- Spinner integration: User feedback during long-running operations
- Better buffering: Output buffering during spinner display
- Log levels: Configurable logging with
--log-levelflag - Improved tracebacks: Enhanced error reporting with full stack traces
Port Management
- ClusterPortManager: Automatic port conflict resolution across clusters
- Dynamic assignment: Intelligent port allocation with increment logic
- Circular dependency handling: Resolves complex multi-cluster port
dependencies
Command Execution Framework
- New
core/exec/package: Structured command execution (host and
container) - Shell auto-detection: Automatically detects available shell in containers
- Environment propagation: Cluster environment variables passed to exec
commands - Better error handling: Clear error messages for failed commands
Configuration & Validation
- Enhanced validation: Pre-flight checks before cluster provisioning
- Config suggestions: Helpful hints using difflib for typos
- Secret scrubbing: Automatic scrubbing of sensitive data (keys, passwords,
tokens) in logs
Other CLI Improvements
- Automatic image builds: No longer need
--docker-native --build; images
build automatically when missing or outdated - Updated Click dependency to 8.1.8
- Better exception handling with structured error types
- Improved snapshot functionality
- Enhanced user feedback and progress indicators
- Cross-platform Docker socket resolution
Library Changes and Additions
New Modules
Admin Modules:
minio: Standalone MinIO object storage module (extracted from dependent
modules)ldap-group-provider: LDAP group provider integrationspooling-protocol: Spooling protocol supportstarburst-gateway: Starburst Gateway orchestrationscim: System for Cross-domain Identity Management (SCIM) integration
Catalog Modules:
stargate: Stargate connector for cross-cluster queriesstargate-parallel: Parallel Stargate connectoriceberg-hms: Iceberg with Hive Metastore support
Security Modules:
kerberos: Kerberos authentication support
Module Updates & Improvements
- All MinIO-dependent modules refactored to use standalone
miniomodule
(#99, #100) - OAuth2 module enhanced with user management and group claims
- Cache service improvements and bug fixes (
results-cachemodule) - LDAP module updated with group information support
- TLS module fixed for multi-cluster environments
- BIAC module bootstrap updated to create
_stubrole - Faker module improvements and compatibility updates
Container Image Enhancements
- Multi-stage Dockerfile: Optimized build with better layer caching
- SDKMAN integration: Flexible Java version management
- Java 24 support: Added mapping for newer Java releases
- Rich toolset: Included curl, jq, netcat, vim, and other utilities
- Non-root execution: Service user for enhanced security
- Safe JVM heap defaults: Configurable heap settings with safe defaults
- Dynamic tarball download: Distribution-aware Trino/Starburst tarball
fetching - Architecture detection: Automatic CPU architecture detection for correct
tarball selection (#97)
Cluster Orchestration
- ClusterProvisioner: Centralized cluster deployment orchestration
- ClusterValidator: Pre-flight validation with comprehensive checks
- Better health checks: Improved container readiness detection
- Coordinator polling: Enhanced startup detection with fail-fast behavior
- Worker provisioning fix: Resolved deadlock issues during worker startup
- Container name resolution: Better handling of worker container names
Module System Improvements
- JSON schema validation: Strict validation of module
metadata.jsonfiles - Dependency resolution: Enhanced module dependency and incompatibility
handling - Module labeling: Better tracking with
org.minitrino.modulelabels - Additive labels: Multi-module containers properly labeled
default_env_keys: Support for default environment variables in metadata- Enterprise detection:...
2.2.4
Minitrino Release Notes: 2.2.4
Release Overview
CLI Changes and Additions
- Update Click dependency to latest release
8.1.8.
Library Changes and Additions
- Added
results-cacheandfakermodules. (#99, #100) - Changed minimum SEP version to 443-e and default version to 468-e.2.
- Updated image's
install.shscript to determine arch type––required to fetch correct release tarball from S3. (#97) - Added temporary workaround for working with legacy and native S3 filesystems in
hive,delta-lake,iceberg, andcache-servicemodules. Trino-native filesystem plugins were enabled by default with release 458 (see: Trino / Starburst release notes), so legacy properties in >= 458 SEP versions need to be replaced with native properties, and in <= 457 releases, legacy properties can continue to be used.
Other
- N/A
2.2.3
Minitrino Release Notes: 2.2.3
Release Overview
CLI Changes and Additions
- Added
--typeoption tomodulescommand. Allows users to specify which type
of modules to display (admin,catalog, orsecurity).
Library Changes and Additions
- N/A
Other
- N/A