Welcome to the Red Book for HPCC Systems® 9.8.x series.
NOTE: We are publishing this Red Book page before the 9.8.0 release so you You can plan any work that may be needed for the Regex changes before upgrading.
You may benefit from glancing at other Red Book entries when making a large jump between releases.
...
To raise an issue, use our Community Issue Tracker. Please create yourself an account if you don't already have one, to get automatic updates as your issue progresses through the workflow.
To ask a developer a technical question about something you are doing or have encountered, post in the Forums on Stack Overflow.
We invite you to post your questions on Stack Overflow utilizing the tag hpcc-ecl (StackOverflow ).To add a note to the RedBook, please contact Jim DeFabia with full details.
Change in Regex Support Library
Starting with 9.8, we now use PCRE2 instead of Boost and ICU. All the libraries are powerful regular expression engines, but they have some key differences that make PCRE2 a better choice for the platform.
...
For more information see: https://www.regular-expressions.info/replacebackref.html:
...
The old Regex libraries allowed illegal "bare" POSIX character class names but PCRE2 does not.
For example:
| Code Block | ||
|---|---|---|
| ||
//If you have this:
REGEXFIND('[:alpha:]', 'Whatever');
//You should now use this:
REGEXFIND('[[:alpha:]]', 'Whatever'); |
The first item is actually beneficial because, more than likely, it produced a silent error. The other three items could require code changes to make existing regex patterns compatible with PCRE2, but the good news is that the changes are compatible with Boost::regex and ICU already. You can make the changes in your code now, before upgrading the platform to 9.8.
For more detailed information, seeChanges to Regex Support in HPCC Systems 9.8.0
Change in LDAP Support
Beginning with 9.8.0, a change in LDAP support may affect your cluster. This section only applies to clusters using the LDAP security manager plugin with caching enabled. Additionally, it only applies if you are using default file scope permissions to grant access to file scopes that are not managed.
...