Skip to main content

Putki 2026.09

Putki 2026.09 is built on Apache Hop 2.19.0 and was released on 17 September 2026. It is the first release with separate editions and without a Putki client: you install Apache Hop from Apache and add the Putki plugins for your edition. How long it is supported is on the support lifecycle page.

The latest patch release is 2026.09.02. Run that one.

What's new​

Editions and downloads​

  • Three editions, each with its own downloads. Basic, Professional and Enterprise each have a release repository on forge.putki.io: putki/putki-dist-basic, putki/putki-dist-professional and putki/putki-dist-enterprise. You see the one your subscription includes. The plugins archive is named after the edition, for example plugins-2026.09-professional.zip.
  • No Putki client. Install Apache Hop 2.19.0 from Apache and add the plugins archive for your edition. Nothing in your projects changes: the same pipeline and workflow files run on Apache Hop with the Putki plugins added.
  • The Putki Marketplace. Install and update Putki plugins from Hop GUI (Tools → Marketplace), with your forge.putki.io account. See Install Putki plugins.
  • The monitoring bundle on every edition's release page: putki-monitoring-2026.09.zip, the Grafana dashboards and logging database for execution monitoring.

Plugins​

  • Preview on the HubSpot, Shopify and Odoo inputs: see the first rows before you run the pipeline.
  • Autodoc: pick the project to document from a list.
  • Lineage graph export (Professional and Enterprise), from the Putki Marketplace.
  • The connectors that call REST APIs (HubSpot, Shopify, Actito, and the Odoo plugin's REST calls) use Apache HttpClient 5. They need Apache Hop 2.19.0: see Breaking changes.

Images and the stack​

  • The images are built on the official Apache Hop images (apache/hop and apache/hop-web 2.19.0) with the Putki plugins added, rather than on a Putki build of Hop.
  • A Grafana image with the Putki dashboards already provisioned (putki-grafana).
  • Neo4j in the stack for execution information, set up from the stack's .env.
  • An optional entry page in front of the stack (the edge profile): one address for every service, with their live status and a read-only view of the schedule.

Breaking changes​

  • The Putki client zip is gone. Install Apache Hop 2.19.0 from Apache, then the plugins for your edition. Upgrade steps are below.
  • The 2026.09 plugins need Apache Hop 2.19.0. The REST-based connectors fail on Apache Hop 2.18 and older. If you have to stay on an older Hop, stay on the plugins of the Putki line built for it.
  • No Beam or Spark in the Putki images. The putki and putki-web images no longer contain the Apache Beam and Spark engines. Pipelines that run with a Beam or Spark run configuration have to run on a Hop installation that has them; Apache Hop from Apache still does.
  • Downloads moved to your edition's repository. putki/putki-dist still carries 2026.09, with the Professional contents, and is not used after this line. Move to your edition's repository now.
  • Maven coordinates are io.putki, no longer bi.know. This only matters if you build against the Putki plugin jars.

Fixed​

  • Putki Web stayed blank after signing in when database (JDBC) authentication was on. This was broken in 2026.06.
  • Neo4j did not start with the settings in the stack's .env.example.
  • The sign-in page showed old branding.
  • Autodoc failed on its first run, could not start on Windows, ran out of memory on large multi-page HTML output, and its dialog could open partly off screen.
  • The Odoo input ignored a renamed field.

Patch releases​

2026.09.02 (29 October 2026)​

2026.09.01 (22 October 2026)​

  • The Grafana image is built on Grafana 13.1.8, with its security fixes.
  • The Neo4j data source plugin is no longer in the Grafana image.
  • On a new installation, the logging database is created again. In 2026.09 it was not, so execution monitoring had nowhere to write on a fresh stack.

Re-issued downloads​

  • Plugins, 24 September 2026. The 2026.09 plugins were rebuilt to fix Autodoc on Windows. If you installed them before that date, replace the plugins/misc/autodoc folder completely: delete it, then unzip the new one. Unzipping over it leaves old libraries behind.
  • The putki-compose-init image, 12 November 2026. The 2026.09, 2026.09.01 and 2026.09.02 images were re-issued without files that did not belong in them. Nothing you use changed. The image has a new digest, so a digest you pinned no longer matches: pull the tag again.
  • SBOMs, 12 November 2026. Every 2026.09 release page now carries a CycloneDX SBOM for each image and plugins archive of your edition: see Get the SBOM for your release.
  • Monitoring bundle. putki-monitoring-2026.09.zip was updated after the release. If the one you have has no bin folder, download it again and follow Upgrade or remove monitoring.

Upgrade from 2026.06​

Hop GUI and Hop on your own machines​

  1. Install Apache Hop 2.19.0: Installing Apache Hop. Install it next to your current Hop rather than over it.
  2. Add the Putki plugins for your edition: Install Putki plugins.
  3. Open your projects in the new Hop. Project files do not change between Hop 2.18 and 2.19.
  4. When everything runs, remove the old Putki client folder.

The Putki stack​

  1. Sign in to the registry with your forge.putki.io account: docker login forge.putki.io.

  2. In the stack's .env, pin the release images:

    PUTKI_REGISTRY=forge.putki.io/putki
    PUTKI_TAG=2026.09.02

    Use the patch release you run. The 2026.09.0 in .env.example is not a tag that exists.

  3. Add the two settings that are new in 2026.09:

    • NEO4J_HTTP_ADVERTISED: the host name and port clients reach Neo4j on, for example localhost:7474. 0.0.0.0 is rejected and Neo4j will not start.

    • WAREHOUSE_DB_PASSWORD: the warehouse database password. It only takes effect when the database is created. On an existing stack, change the password in the running database first:

      docker compose exec warehouse-db psql -U developer -d warehouse \
        -c "ALTER USER developer WITH PASSWORD '<new>'"

  4. Pull and restart: docker compose pull, then docker compose up -d.

  5. If you use Beam or Spark run configurations, move those runs to a Hop installation that has the engines (see Breaking changes).

Known issues​

  • .env.example suggests PUTKI_TAG=2026.09.0, which does not exist. Use 2026.09.02.