[
https://issues.jboss.org/browse/ISPN-3795?page=com.atlassian.jira.plugin....
]
Sanne Grinovero commented on ISPN-3795:
---------------------------------------
I know, that's why I'm referring to it: since you fixed that, I'm assuming
you're aware of the kind of special considerations we need to apply in this area: we
can't allow users to play with random flags as there are various complexities which
need to be taken care of.
QueryInterceptor incorrectly relies on the return value of a
RemoveCommand
--------------------------------------------------------------------------
Key: ISPN-3795
URL:
https://issues.jboss.org/browse/ISPN-3795
Project: Infinispan
Issue Type: Bug
Components: Querying
Affects Versions: 6.0.0.Final
Reporter: Dan Berindei
Assignee: Sanne Grinovero
Fix For: 7.0.0.Final
QueryInterceptor uses the return value from RemoveCommand/ReplaceCommand to remove the
value from the index.
But both RemoveCommand and ReplaceCommand have a variant with an expected value
parameter, and this variant return a boolean value instead of the removed/replaced value.
In that case, the previous value won't be removed from the index.
QueryInterceptor should probably use the previous value from the context entries to
update the index instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira