Although there is no single theme to YottaDB r1.32, it qualifies as a major release because it includes a significant number of enhancements, including several to enable the Application Independent Metadata plugin (
https://gitlab.com/YottaDB/Util/YDBAIM)
plugin. The plugin provides functionality for applications to push responsibility for maintaining cross references and statistics to YottaDB triggers, thereby reducing the code that applications must maintain. We will tell you more about the AIM plugin
in the near future. Enhancements include:
- The $ZYSUFFIX() function enables applications to create variable and routine names that are guaranteed for all practical purposes to be unique, as it uses all 128 bits of the 128-bit MurmurHash3 (
https://en.wikipedia.org/wiki/MurmurHash#MurmurHash3)
non-cryptographic hash to create a 22-character string which can be appended to a string like "MyApp" to create legal variable and routine names.
- A $ZPARSE() option to follow symbolic links.
- Sourcing ydb_env_set creates and manages a three-region database, and defaults to UTF-8 mode.
- An option to allow $ZINTERRUPT to be invoked for the USR2 signal.
- The --aim option of ydbinstall / ydbinstall.sh installs the Application Independent Metadata plugin.
- Shell-like word expansion with $VIEW("WORDEXP").
- Propagation downstream of context set by triggers.
- ydb_ci_*() functions return the ZHALT argument for C code that calls M code which terminates with a ZHALT.
From the upstream GT.M V6.3-009 (
http://tinco.pair.com/bhaskar/gtm/doc/articles/GTM_V6.3-009_Release_Notes.html) and V6.3-010 (
http://tinco.pair.com/bhaskar/gtm/doc/articles/GTM_V6.3-010_Release_Notes.html), which are included in the r1.32 code base,
there are enhancements to operational functionality.
There are numerous smaller enhancements that make system administration and operations (DevOps) friendlier, and easier to automate. For example, %PEEKBYNAME() has an option to query global directory segments without opening the corresponding database
files; orphaned relinkctl files are automatically cleaned up; and the --octo option of ydbinstall / ydbinstall.sh installs Octo such that octo --version reports the git commit hash of the Octo build.
As with any YottaDB release, there are numerous other enhancements and fixes, some specific to YottaDB (including fixes to issues discovered while merging and testing the upstream code), and others inherited from the upstream code. Details are in the
Release Notes (
https://gitlab.com/YottaDB/DB/YDB/-/tags/r1.32).
YottadB r1.32 is upward compatible with YottaDB r1.30 (
https://gitlab.com/YottaDB/DB/YDB/-/tags/r1.30), GT.M V6.3-009 (
http://tinco.pair.com/bhaskar/gtm/doc/articles/GTM_V6.3-009_Release_Notes.html), and GT.M V6.3-010 (
http://tinco.pair.com/bhaskar/gtm/
doc/articles/GTM_V6.3-010_Release_Notes.html).
Please try YottaDB r1.32 and tell us what you think, and please plan to upgrade to r1.32 at your convenience.
You may have noticed that we have moved to a Continuous Integration / Continuous Delivery (CI/CD) model for most of our software, with a couple of exceptions. One set of exceptions is simple utilities such as gvstat (
https://gitlab.com/YottaDB/Util/
YDBGvstat), for which we just have not yet invested the effort to migrate to a CI/CD model, but will by and by. At the other end is YottaDB, which has been moving to a CI/CD model, but is not there yet. After the release of r1.32, we plan to merge https:/
/gitlab.com/YottaDB/DB/YDB/-/merge_requests/1011 to bring CI/CD to YottaDB itself, at least for development and testing environments. YottaDB will continue to retain formal releases for production environments. This is because the extensive testing
required for our production releases takes several days on a group of a couple dozen machines working together, and involves stress tests, crash tests, and other tests that are not practical in a CI pipeline.
Thank you for your interest in YottaDB.
Regards
– Bhaskar
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)