Versioning of the Internal BPC Configuration
The BPC stores its configuration internally in the OpenSearch under the index bpc-configuration.
The current state 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, during a BPC update, the internal configuration changes and the version number is incremented as a result, the BPC automatically migrates the existing configuration to the new version and stores the new version number in the index.
Potential Impact on Operations
The version of the internal configuration affects certain aspects of operations.
Deployment
It is not possible to perform a Deployment from a BPC with a higher model_version to a BPC with a lower model_version.
However, it is possible to perform a deployment from a BPC with a lower model_version to a BPC with a higher model_version.
If necessary, configuration adjustments are made automatically during this process.
Downgrade
Additional steps are required to perform a BPC downgrade if the target version of the BPC uses a lower model_version.
See: Downgrade Guide
Retrieving the Current Version Number
The version number is stored in the metadata of the bpc-configuration index.
It can be viewed directly in BPC at OpenSearch Index View.
It is included in the index’s mapping information and is listed there as model_version.
bpc-configuration indexAlternatively, this information can also be retrieved directly via OpenSearch at the URL https://SERVER:PORT/bpc-configuration?pretty.
This information can also be found there under 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 for authentication with OpenSearch can be found on the Direct OpenSearch Access page. |