Versioning of the internal BPC configuration
The BPC stores its configuration internally in OpenSearch under the index bpc-configuration.
The status of this configuration is assigned a fixed version number internally.
This is stored internally as model_version in the index and is a natural number that is incremented in the event of an update.
If the internal configuration changes during a BPC update, thereby increasing the version number, the BPC automatically migrates the existing configuration to the new status and stores the new version number in the index.
Potential impact on operation
The version of the internal configuration has an impact on some aspects of operation.
Deployment
It is not possible to carry out a Deployment from a BPC with a higher model_version to a BPC with a lower model_version.
However, it is possible to deploy from a BPC with a lower model_version to a BPC with a higher model_version.
If necessary, adjustments to the configuration are carried out automatically.
Downgrade
It requires additional steps to downgrade the BPC if the target version of the BPC uses a lower model_version.
See for this: Downgrade Guide
Reading out the current version number
The version number is stored in the metadata of the bpc-configuration index.
This can be viewed directly in the BPC at OpenSearch indices view.
It is contained in the mapping information of the index and is called model_version.
bpc-configuration indexAlternatively, this information can also be queried directly via OpenSearch at the URL https://SERVER:PORT/bpc-configuration?pretty.
This information can also be found there at model_version.
curl --insecure -u USER:PASSWORT 'https://localhost:9200/bpc-configuration?pretty'
{
"bpc-configuration_1739522947935" : {
"aliases" : {
"bpc-configuration" : { }
},
"mappings" : {
"_meta" : {
"model_version" : 24
}
}
}
}
|
Examples of authentication against OpenSearch can be found on the page Direct OpenSearch access. |