Previously there was no check if DC name provided in the policy (DCAware and RackAware) is correct. That could lead to e.g. making routing decisions based on the wrong DC name.
This PR introduces failing to connect if DC name is different in the topology than the one the user entered.
@mykaul @Lorak-mmk
I pushed the new version with IsOperational(*Session) error API and additional check for rack. Is it what you had in mind @dkropachev ?
Previously there was no check if DC name provided in the policy (DCAware and RackAware) is correct. That could lead to e.g. making routing decisions based on the wrong DC name.
This PR introduces failing to connect if DC name is different in the topology than the one the user entered.
Fixes: #205