FMR 11 to FMR 12¶
FMR 12 introduces significant changes to the database schema and and the system configuration parameters. For this reason, it's not possible to to directly upgrade an existing FMR 11 installation to version 12. Instead a separate FMR 12 installation must be created with an empty database and the content migrated.
The recommended content migration method is to use the backup and restore process which importantly:
- preserves the structure change history and audit records;
- copies reference metadata reports (aka metadatasets); and
- copies data registrations
On import, FMR 11's change history is reorganised into FMR 12 metadata time allowing past registry states to be queried using the metadata time travel feature.
Behaviour changes between FMR 11 and FMR 12¶
Semantic and non-semantic structure cross referencing¶
The introduction of full semantic versioning support in FMR 12 changes the cross-referencing behaviour.
Important
Specifically, semantically versioned structures, those with three-part version numbers such as 1.3.2, will no longer reference non-semantically versioned children with two-part version numbers like 1.0.
This is because stable semantically versioned artefacts may only in turn reference stable artefacts. Non-semantically versioned artefacts are implicitly considered unstable since they may be modified without changing the version number.
Example:
A DSD in an FMR 11 registry ACY:MACRO_ECONOMICS(1.3.2) references a Codelist ACY:CL_INDICATOR(1.0). In FMR 12, this will be rejected because the DSD is considered to be a stable semantic version in contrast to the Codelist which is unstable.
Structure query using '+' and '~' version wildcard operators¶
FMR supports the SDMX v2.0+ structure query REST API, including semantic wildcard queries for version selection using the + and ~ operators.
Examples: