Key questions about this property
The answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? |
Sets the upper bound used to validate partition counts, with a default maximum of 32 when no value is set. |
| What area does it affect? |
Kafka partition configuration |
| What does the default mean? |
No out of the box record exists and the scripts that read it pass no fallback value. |
| When should you review it? |
When changing the permitted maximum partition count |
Property record
No out of the box record exists. ServiceNow scripts read this property; create it to change the behavior.
| Property name |
com.glide.maximum_partitions |
| Type |
Not stated |
| Application |
Not stated |
| Default value |
Not set |
| Description |
Not stated |
Sources
Official references and nearby text excerpts where this property appears.
Used in
Out of the box artefacts that read this property. Append the path to your instance URL to open the record and see how the value is used.
Business rule: Update Partition Count
The rule reads this property as the maximum allowed partition count and blocks an update above that limit, showing an error with the allowed range. If the property is unset or no value is supplied, the limit defaults to 32.
/sys_script.do?sys_id=38984b97430131103464827cfbb8f295
Business rule: Validate kafka partitions
The rule reads this setting to set the allowed partition range and the validation error shown when a user enters a value outside that range; invalid entries also clear the name and namespace and reset partitions to 1. If no value is set, the maximum defaults to 32.
/sys_script.do?sys_id=36d0f8f1ff2121105cf343d0653bf1d8
More in com.glide
Other properties in the same namespace.
All 909 properties in com.glide →