As it stands, cluster ids aren't being utilized for anything other than to be added to a cluster upon creation as well as being added to the cache file. They are there for a reason so need to start incorporating them into the project more
Need to:
[x] Make a system that validates that all cluster ids found in a collection are also found in the cache file before performing operations on said collection. This will act as the first step in the overall data validation process. Doing this will ensure that a user cannot just go in, modify a cluster id to something random then perform operations via the OstrichDB command line.
[x] Remove cluster ids from the cache file when a cluster is deleted.
[x] If a cluster Id is in a collection but it is NOT found in the cache file. That collection has lost its data integrity from the jump.
As it stands, cluster ids aren't being utilized for anything other than to be added to a cluster upon creation as well as being added to the cache file. They are there for a reason so need to start incorporating them into the project more
Need to:
[x] Make a system that validates that all cluster ids found in a collection are also found in the cache file before performing operations on said collection. This will act as the first step in the overall data validation process. Doing this will ensure that a user cannot just go in, modify a cluster id to something random then perform operations via the OstrichDB command line.
[x] Remove cluster ids from the cache file when a cluster is deleted.
[x] If a cluster Id is in a collection but it is NOT found in the cache file. That collection has lost its data integrity from the jump.