Hop 1.1.0 - Apache Hop continues to mature.

Apache Hop 1.1 Released

Apache Hop contains about 4 months of work on 235 tickets by the Apache Hop Community.

Hop 1.0.0 was mainly a showcase release that contained all the refactoring and functionality the Apache Hop community had been working on for over 2 years. Now, four months and one graduation later, the Hop 1.1.0 release is further proof of the coming of age of Apache Hop as a platform, as a project and as a community.

Point releases like Hop 1.1.0 bring evolution rather than revolution. Nevertheless, Hop 1.1.0 brings quite a lot of good stuff, let’s walk through what you can expect in this release.

Improved robustness, stability and performance

Hop’s growing popularity is reflected in the number of people that test Hop releases and find and report bugs.

Hop’s growing library of integration tests guarantees that a bug, once fixed, remains fixed. With these integration tests, which run every night on the Hop build server, Hop eats its own dog food. The integration tests use Hop workflows and pipelines to test Hop workflows and pipelines. The integration tests are not limited to the Hop build, but can serve as a blueprint to set up integration testing for your own projects.

The never ending bug hunt and quest for clean code have resulted in a Hop platform that is increasingly stable and robust.

New and Notable features

Hop Server

Hop Server now supports projects and environments, asynchronous web services for long-running workflows and pipelines, and can be started with SSL.
Hop 1.1.0 also comes with a new transform that lets you query the server status from within a pipeline.


The default Hop Docker container now supports optional support for projects and environments in both the long- and short-lived container. The container now contains additional support for logging variables and returns improved exit codes.

Apache Beam

Apache Beam has been upgraded to 2.35.0, with support for Apache Spark 3.1.2 and Apache Flink 1.13.5. Service accounts on Google Cloud Dataflow are now supported, as is the DataflowServiceOptions, which pass various options through if they’re not available in the GUI

New and improved plugins
  • Hop Server Status: retrieves a lot of server and operating system metrics from one of your Hop Servers.

  • Apache Tika: parses files in all sorts of formats and extracts the text content as well as available metadata it can extract.

  • Metadata input: gives you access to the Hop Metadata items in the current project. It outputs all the metadata objects of all types unless one or more types are filtered.

  • Neo4j Graph Output: now supports models with multiple relationships between two nodes, with multiple node labels and with self-relationships

  • Hop Gui has seen lots of tiny improvements that together make it a lot easier and more productive to develop or work with workflows and pipelines. These improvements include lazy file loading, reinstated git file status color coding, editable text files and more.

  • Log4j was completely removed

  • Kafka consumer and producer improvements

All the details are available in the official Apache Hop 1.1.0 release announcement.


Hop’s following on social media has increased between 25% and 75%. The number of contributors, contributions, website visitors and downloads have all grown increasingly since the 1.0 release and even more so since the graduation as a Top-Level Project.

A healthy, respectful and growing community is indispensable for the success of an open source project like Apache Hop. The Hop community checks all of these boxes and is one of the reasons why Hop is a thriving and growing platform with a bright future ahead.

Lean With Data and Apache Hop 1.1.0.

As the Apache Hop platform and community continues to grow, so does Lean With Data.

As the original Apache Hop project founders and PMC members, we will continue to actively sponsor, work on and contribute to the Apache Hop platform.

We’re working on more and improved ways to support our customers from development over testing to successful production deployments, with a lot of attention for best practices and well-implemented solutions.

Every single Hop release already is supported through our Lean Orchestration packages, but we’re aiming higher. More on that soon, so watch this space.

In the meantime, reach out if you’d like to learn more about how you can get the most out of Apache Hop for your organization.

Blog comments

related posts