Today we can only specify an absolute number in the 'replica' attribute in the policy rules. It'd be useful to write a percentage value to make certain use-cases easier. For example:
Today the above must be represented by different rules for each collection if they have different replication factors. Also if the replication factor changes later, the absolute value has to be changed in tandem. So expressing a percentage removes both of these restrictions.
This feature means that the value of the attribute "replica" is only available just in time. We call such values "computed values" . The computed value for this attribute depends on other attributes as well.
Take the following 2 rules
assume we have collection "A" with 2 shards and replicationFactor=3
example 1 would mean that the value of replica is computed as
3 * 34 / 100 = 1.02
Which means for each shard keep less than 1.02 replica in east availability zone
example 2 would mean that the value of replica is computed as
3 * 2 * 34 / 100 = 2.04
which means for each collection keep less than 2.04 replicas on east availability zone