Content Server Manual / Version 2107
Table Of ContentsSometimes it might be necessary to change the size of a string property. For example, when the size exceeds a database limit.
Prerequisites
Be sure that you have a backup of your data. When you want to reduce the length, make sure that all existing content fits into the new size.
Caution
When the StringProperty is observed, the length must not exceed 256.
Otherwise, the content server cannot start and you will see a log entry like the following in the content server log:
2018-12-10 15:01:38 [ERROR] hox.corem.server.Server [] - \ Cannot startup due to malformed document type definition: \ The length 257 of the observed StringProperty 'observed' exceeds the allowed maximum length 256 (Init Process)
Proceed as follows:
Be sure to have a backup of your data.
Stop the Content Server.
Change the
Lengthattribute to the new length.Make sure that property
sql.schema.alterTableis set to true.Start the Content Server again.
You should see log entries like the following in the content server log.
2018-08-22 13:33:11 [INFO] hox.corem.server.sql.SQLStore [] - \ SchemaValidator: validating document types (Init Process) 2018-08-22 13:33:11 [INFO] hox.corem.server.sql.SQLStore [] - DocumentTypeRegistry: altering table: \ ALTER TABLE CMAction MODIFY "teaserTitle" VARCHAR(300) (Init Process) 2018-08-22 13:33:11 [INFO] hox.corem.server.sql.SQLStore [] - DocumentTypeRegistry: altering table: \ ALTER TABLE ESDynamicList MODIFY "teaserTitle" VARCHAR(300) (Init Process)
Example 4.8. Log entries when string property has been changed
