The store-identity is implemented as part of the backend protocol but is not used in assessing if configurations are equivalent. As a result two stores are functionally equivalent are not be deemed so unless they are literally equivalent. This fix uses the store-identity to check equivalence for configurations and connections.
e.g. on JDBC these two stores are equivalent but not be deemed so. They appear different as because in one case the DB and datahike are on the same network and the in the other they are not.
alekcz
commented
9 months ago
SUMMARY
The
store-identityis implemented as part of the backend protocol but is not used in assessing if configurations are equivalent. As a result two stores are functionally equivalent are not be deemed so unless they are literally equivalent. This fix uses thestore-identityto check equivalence for configurations and connections.e.g. on JDBC these two stores are equivalent but not be deemed so. They appear different as because in one case the DB and datahike are on the same network and the in the other they are not.
Bugfix