We are pleased to announce the 1.3.0. M2 release of the Spring Cloud Data Flow and its associated ecosystem of projects.
Local Server: Getting Started Guide.
In this second installment of 1.3 release of Dashboard/Flo, we have addressed the core functionalities backing the streaming and task/batch operations.
Continuing the Angular4 based infrastructure upgrades, the streaming and task/batch workflows now include the modern look and feel and are packed with usability improvements as well.
Due to the popular demand from the community, customers, and field, this release includes support for fan-in and fan-out visual representation of data pipelines. The following image shows fanning at work:
As an addition, there is a new control to directly branch out from a specific node to TAP the stream from that position.
Likewise, there’s also an option to switch the primary stream within the topology. It is just one click away - its that simple!
Spring Cloud Data Flow always included support for data pipelines that interact with named-destinations as a producer, a consumer, or both. This release adds the ability to interact with them visually, and it makes building a complex topology easier. There can be “n” combinations of producers and consumers connected to a common destination, which is very powerful for architectures involving wide variety of data sources and destinations. The following image shows an example of a complex topology:
Users who are resolving maven artifacts from a public or private maven artifactory can now take advantage of the “update-policy” feature. You can use this ability to override and refresh Spring Cloud Data Flow’s internal maven cache. For instance, in development, you can continuously resolve SNAPSHOT versions of the maven artifact by setting
update-policy=always, which will force the download of the latest version of the streaming or batch/task application that’s in use in the DSL/Dashboard.
Given the traditional and OAuth security support in Spring Cloud Data Flow and the requirement to have the similar coverage for its companion servers such as spring-cloud/spring-cloud-dataflow-metrics-collector, spring-cloud-task-app-starters/composed-task-runner, and the soon-to-be-released spring-cloud/spring-cloud-skipper, we have extracted the common security infrastructure into a standalone library. The spring-cloud/spring-cloud-common-security-config library will be reused in companion servers in future releases.
This release adds “autocompletion” for stream and task/batch names and other metadata. No more guessing - everything is a TAB press away! Check out the following screencast to learn more about the advanced shell features, tips, and tricks:
This release brings the Spring Boot 1.5.7 compatibility and the underlying Spring Cloud infrastructure is updated to Dalston.SR3. For more details, please review the 1.3.0 M2 release notes.
Looking ahead, we are aiming for 1.3.0 M3 followed by the release candidate and then the general availability release by October 2017.
Please try it out, share your feedback, and consider contributing to the project!