Automic VaultAutomic Vault

brew

Install kettle with Homebrew

Pentaho Data Integration software. Version 9.4.0.0-343 via Homebrew; verified from local package data.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install kettle

local Homebrew formula metadata

overview

Package summary

Pentaho Data Integration software

Commands and aliases

  • pdicarte
  • pdikitchen
  • pdipan

history

Project history and usage

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.

Project history

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.

Adoption history

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.

How it is used

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.

Why package nerds care

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.

Timeline

  • 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.

security posture

Risk level: orange

formula declares a Homebrew service.

Risk classifier

orange risk · medium confidence · infrastructure

Why

  • formula declares a Homebrew service

Signals

  • metadata:service

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Formula metadata declares a service or daemon block.
  • Homebrew bottle metadata is available for 1 platform targets.
  • Installs with 1 runtime dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

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

Installed executables

CommandKindExposureNote
pdicartecliglobal executable
pdikitchencliglobal executable
pdipancliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08
manager version9.4.0.0-343
manager updated
local dataok
upstreamnot checked
latest detectednot detected

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

install metadata

Package metadata

Package keybrew:kettle
Version9.4.0.0-343
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/kettle
Homepagehttps://pentaho.com/products/pentaho-data-integration
Repositoryhttps://github.com/pentaho/pentaho-kettle
Upstream docshttps://docs.pentaho.com/pdia-data-integration/10.2-data-integration
LicenseApache-2.0
Source archivehttps://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
Dependenciesopenjdk
Bottleavailable (on all)
Homebrew post-installnot defined
Servicedeclared

registry facts

Source database details

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

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • 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