HPCC Systems 7.2.0 now available for download

[lchapman]

We are very pleased to announce that HPCC Systems 7.2.0 is now available for download.

View the release notes for the full list of changes. The supporting documentation is available on our website and we recommend that you browse the RedBook for additional information about specific items of note. Highlights of this release include:

IDE Improvements

• Auto Completion
• Expired password

Java Embed Improvements

• Support for inline embedded code
• Persistence options
• Passing of Java objects to embedded code
• Sharing of classes using the same classpath
• Jar file manifest feature
• Improved exception reporting
• Read a blog about Embedded Java Enhancements in HPCC Systems 7.2.0 by Richard Chapman

Alternative way of embedding C and C++ Code
Allows files of embedded code rather than snippets. These can be disabled or allowed based on whether there they are signed. Provides a new, more convenient way of allowing embedded code in a secure way.

• Manifest support for signed code
• Option to disable code in manifest
• Specify CPP sources via manifest file

Spark improvements and features

• Implement functionality to write datasets to HPCC Systems from remote Spark clusters.
  Includes: Support for all ECL types and create file overwrite functionality
• Enhanced pyspark dataset read support
• Provide JAVA based DFS Client
• Enhance Spark connector read/write functionality by decoupling logic extending dafilsrv client
• Significantly decreased overall size footprint of HPCC Systems java clients

Std date additions

• Datetime difference
• ISO week dates

Thor new feature - Taking the load off Thor for jobs that don’t need to go to Thor

Geo spatial library from Uber - Now available as a plugin to allow it to be used from ECL code

View the full list of new features / full list of issues fixed in HPCC Systems 7.2.0.

Have questions or need a tip? Post in our Developer forum.
Found an issue or have a feature request? Raise a JIRA issue.
Want to contribute? Walk through the process and take a look at the notes for developers included in the readme in our GitHub repository.