[ https://issues.jboss.org/browse/ISPN-7990?page=com.atlassian.jira.plugin.... ] Sanne Grinovero edited comment on ISPN-7990 at 6/28/17 7:01 AM: ---------------------------------------------------------------- Remember that if you don't know the type this is problematic: * you won't know which indexes need to be cleaned up (can't match the sharding strategy) * even cleaning up "all indexes" by id is troublesome as you might not have a full list to define "all indexes" * without the type you don't know how to encode the key -> not matching the right key might lead to various mismatches, like delete the wrong data or not deleting it at all The only safe solution I see is to know upfront which types might be used in this Cache; even so, what if the index was created by an instance having a different / out of date configuration ? was (Author: sannegrinovero): Remember that if you don't know the type this is problematic: * you won't know which indexes need to be cleaned up * even cleaning up "all indexes" by id is troublesome as you might not have a full list to define "all indexes" * without the type you don't know how to encode the key -> not matching the right key might lead to various mismatches, like delete the wrong data or not deleting it at all The only safe solution I see is to know upfront which types might be used in this Cache; even so, what if the index was created by an instance having a different / out of date configuration ? -- This message was sent by Atlassian JIRA (v7.2.3#72005)