Added Test Case for Synchronizing Multiple Cache with Namespace #36
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces a new test case to handle synchronization of multiple caches with namespaces, which is currently not addressed. The test verifies if changes made in one cache (within a specific namespace) are propagated correctly across other caches created with the same configuration.
Issue:
The test case fails because the namespace is not being properly cleared across all caches. When a key is deleted from the namespace in one cache, it should be deleted across all caches, but currently, the data remains in some of the caches.
Impact:
This issue can lead to inconsistent data across multiple caches when working with namespaced data. This pull request aims to highlight the need for synchronization of cache data across instances within the same namespace.