[
https://issues.jboss.org/browse/ISPN-3795?page=com.atlassian.jira.plugin....
]
Adrian Nistor commented on ISPN-3795:
-------------------------------------
+1 for ignoring IGNORE_RETURN_VALUE when it prevents query work, even if that means we
could loose a bit of perf.
Let me remind you that continuous query also needs the previous value in order to work.
That's a totally different subject, but my point is we need to accept some trade-offs
when using certain features, like query, which will inevitably slow things down a bit.
We could digress into arguing if caches need to be typesafe or not, but that would still
not solve the CQ issue.
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: Embedded Querying
Affects Versions: 6.0.0.Final
Reporter: Dan Berindei
Assignee: Gustavo Fernandes
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 was sent by Atlassian JIRA
(v7.2.3#72005)