After four months of work on well over 200 tickets, the Apache Hop PMC and 
community are pleased to announce the general availability of Apache Hop 1.1.0.
This 1.1.0 release is the result of a massive effort by the Apache Hop 
community.

The Hop Orchestration Platform, or Apache Hop, aims to facilitate all aspects 
of data and metadata orchestration.
Hop is an entirely new open source data integration platform that is easy to 
use, fast and flexible.
Hop aims to be the future of data integration. Visual development enables 
developers to be more productive than they can be through code. Our Design 
once, run anywhere workflows and pipelines can be designed in the Hop Gui and 
run on the Hop native engine (local or remote), or on Spark, Flink, Google 
Dataflow or AWS EMR through Beam.
Lifecycle Management enables developers and administrators to switch between 
projects, environments and purposes without leaving your train of thought.

A number of highlights in the 1.1.0 release are:
- Hop Server now supports SSL, projects and environments, and asynchronous web 
services
- the Docker image now (optionally) supports projects, environments and logging 
options
- Apache Beam is updated to 2.35.0 with support for Apache Spark 3.1.2 and 
Apache Flink 1.13.5, service accounts for Google Cloud Dataflow and 
DataflowServiceOptions.
- new transform plugins: Hop Server Status, Metadata Input, Apache Tika
- major updates to the Neo4j Graph Output transform to support more complex 
graphs
- lots of Hop Gui improvements to work with large workflows and pipelines, lazy 
file loading and a warning when opening large files
- Log4j is now completely removed
- lots of other improvements for Apache Kafka, CockroachDB, 
internationalization, documentation and more
- community growth

The release is available for immediate download at:

https://hop.apache.org/download/

For more details please take a look at the release announcement at:

https://hop.apache.org/blog/2022/01/hop-1.1.0/

Thanks to all involved,
Bart Maertens on behalf of the Apache Hop PMC

Reply via email to