Release Notes / Version 12.2406.0
Table Of Contents
To be able to use human-readable capacity configurations such as
1GB in favor of 1_073_741_824
given as bytes, a bunch of properties got transformed to hold
DataSize instead of long or
int values denoting bytes, for example.
The following is a list of affected properties that benefit from this change:
com.coremedia.transformcom.coremedia.transform.blob-cache.size
management.healthmanagement.health.blobCacheDiskspace.thresholdmanagement.health.transformedBlobCacheDiskspace.threshold
repositoryrepository.blob-streaming-size-thresholdrepository.blob-cache-sizerepository.heap-cache-sizerepository.max-cached-blob-size
studiostudio.differencing.max-markup-size
sqlsql.store.sgml-cache-size(renamed from:sql.store.sgml-cache-size-bytes; old name still applicable)
workflowworkflow.blob-streaming-size-thresholdworkflow.blob-cache-sizeworkflow.heap-cache-sizeworkflow.max-cached-blob-size
Upgrade Information
In general no additional upgrade steps should be required.
Nevertheless you may experience incoming changes especially to our
default application.properties we ship with
CoreMedia Blueprint, where we changed respective properties to the
human-readable form.
Properties using the old unitless format are still supported and use the same default unit as they did before.
In addition to that, some ConfigurationProperties
that ship with CoreMedia Blueprint have been adjusted. This applies to
the following classes:
com.coremedia.blueprint.transform.boot.autoconfigure.CoremediaTransformHealthIndicatorAutoConfigurationcom.coremedia.blueprint.boot.autoconfigure.HealthIndicatorAutoConfiguration
(CMS-22469)
