[
https://issues.jboss.org/browse/ISPN-7990?page=com.atlassian.jira.plugin....
]
Gustavo Fernandes commented on ISPN-7990:
-----------------------------------------
bq. you won't know which indexes need to be cleaned up
That's the issue this JIRA is trying to address. As I found out recently, there are
some corner cases (considered rare, during state transfer) where it's not possible to
know the type.
bq. even cleaning up "all indexes" by id is troublesome as you might not have a
full list to define "all indexes"
I assume the QueryKnownClasses object would have all types stored? If not, doesn't the
searchFactory know about all existent indexes?
bq. 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 key encoding is done by the KeyTransformationHandler which is cache-scoped; so I
assume the id is consistent across all indexes.
bq. what if the index was created by an instance having a different / out of date
configuration
How this could happen? I have a feeling if clusters have caches with outdated
configurations indexing would not be the only problem
Provide a way to remove an entry from all indexes
-------------------------------------------------
Key: ISPN-7990
URL:
https://issues.jboss.org/browse/ISPN-7990
Project: Infinispan
Issue Type: Enhancement
Components: Embedded Querying
Affects Versions: 9.1.0.Beta1
Reporter: Gustavo Fernandes
Assignee: Gustavo Fernandes
This may be needed in some non frequent scenarios (happening during topology changes)
where a write command cannot obtain the previous value to remove it from the index.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)