When we use the default MountTableResolver to resolve the path, we cannot get the destination paths for the default DestinationOrder.HASH.
The default order will be hash, but the HashFirstResolver will not be invoked to order the location.
It is ambiguous for the MountTableResolver that we will see the HASH order in the web ui for multi-destinations path but we cannot get the result.
In my opinion, the MountTableResolver will be a simple resolver to implement 1 to 1 not including the 1 to n destinations. So we should check the buildLocation. If the entry has multi destinations, we should reject it.