Automic VaultAutomic Vault

brew

kettle mit Homebrew installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für kettle in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install kettle

local Homebrew formula metadata

Überblick

Paketzusammenfassung

Pentaho Data Integration software

Befehle und Aliase

  • pdicarte
  • pdikitchen
  • pdipan

Verlauf

Projektgeschichte und Nutzung

Pentaho Data Integration, still widely known by its original project name Kettle, is one of the long-running open-source ETL tools from the Java business-intelligence era. It matters in package catalogs because the command-line launchers let scripted jobs run transformations and workflows that are often designed in a graphical ETL environment.

Projektgeschichte

Matt Casters began Kettle as a platform-independent ETL project before releasing it as open source in December 2005. The project joined Pentaho soon afterward and became the data-integration component of the Pentaho platform, while the Kettle name stayed attached to the repository, file formats, user community, and command-line tools.

After Pentaho became part of Hitachi Data Systems in 2015, the public code continued in the pentaho-kettle GitHub repository under the Pentaho Data Integration name. The repository structure reflects a large Java application: assemblies for distribution, core and engine modules, UI modules, plugins, and integration tests.

Adoptionsgeschichte

Kettle gained adoption as a visual ETL tool in the Pentaho ecosystem, with community downloads distributed through SourceForge and commercial editions distributed through Pentaho/Hitachi channels. Its command-line tools made it attractive to operations teams that wanted GUI-authored data flows scheduled from cron, shell scripts, or enterprise schedulers.

In late 2019 Apache Hop started as a fork of Kettle/Pentaho Data Integration. Hop later diverged into an independent Apache project, but its migration documentation is evidence of the amount of Kettle/PDI project work accumulated in the field.

Wie es verwendet wird

Package users typically care about pdipan, pdikitchen, and Carte-style execution rather than the full desktop experience: those launchers run transformations, jobs, and remote execution services from files or repositories. The package is therefore part data-engineering tool and part compatibility layer for older Pentaho deployments.

Warum Paket-Nerds sich dafür interessieren

Kettle is a good example of a GUI-first enterprise data tool that still belongs in Unix package indexes because its real production surface is scriptable. It also preserves a recognizable lineage from early open-source BI through modern data-orchestration projects such as Apache Hop.

Zeitleiste

  • 2001: Matt Casters began work on the ETL tool that became Kettle.
  • 2005-12: Kettle was released as open source.
  • 2006: Kettle joined the Pentaho project and became Pentaho Data Integration.
  • 2015: Hitachi Data Systems acquired Pentaho.
  • 2019: Apache Hop began as a fork of Kettle/Pentaho Data Integration.

Related projects

  • Pentaho Business Analytics and Hitachi Vantara Pentaho are the surrounding platform family. Apache Hop is the most important descendant project, initially forked from Kettle/PDI and later developed on an independent roadmap.

Sicherheitslage

Risikostufe: orange

formula declares a Homebrew service.

Risikoklassifikator

orange Risiko · mittel Konfidenz · infrastructure

Warum

  • formula declares a Homebrew service

Signale

  • metadata:service

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Formelmetadaten deklarieren einen Service- oder Daemon-Block.
  • Homebrew-Bottle-Metadaten sind für 1 Plattformziele verfügbar.
  • Installiert mit 1 Laufzeitabhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix
~/kettle.properties~/.pentaho/kettle.properties~/.kettle/repositories.xml

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
pdicartecliglobales Executable
pdikitchencliglobales Executable
pdipancliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-25
Manager-Version9.4.0.0-343
Manager aktualisiert
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://pentaho.com/products/pentaho-data-integration

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:kettle
Version9.4.0.0-343
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/kettle
Homepagehttps://pentaho.com/products/pentaho-data-integration
Repositoryhttps://github.com/pentaho/pentaho-kettle
Upstream-Dokumentationhttps://docs.pentaho.com/pdia-data-integration/10.2-data-integration
LizenzApache-2.0
Quellarchivhttps://hitachiedge1.jfrog.io/artifactory/pntpub-maven-release/org/pentaho/di/pdi-ce/9.4.0.0-343/pdi-ce-9.4.0.0-343.zip
Abhängigkeitenopenjdk
Bottleverfügbar (auf all)
Homebrew post-installnicht definiert
Dienstdeclared

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namekettle
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedyes
Disabledno
Keg Onlyno
URL Keys
  • stable

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment