[
https://issues.apache.org/jira/browse/GEODE-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15423663#comment-15423663
]
ASF subversion and git services commented on GEODE-1745:
--------------------------------------------------------
Commit 5da6c7e5e55f18a6ff520dbca12e65ac88dd4015 in incubator-geode's branch
refs/heads/feature/GEODE-1781 from [~nnag]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=5da6c7e ]
GEODE-1745: Fixed the comparison during query re-evaluation using
CompactMapRangeIndexes
* Initially the object to be searched was compared with the tuple
returned by the Compact Range Index which contains the object to be searched
and a key
* This led to mismatch to occur resulting in false query results.
* Fixed to compare with the first element of the tuple returned by the
compact range index.
> In case of Compact Map Range Index, query reevaluation results in false
> results
> -------------------------------------------------------------------------------
>
> Key: GEODE-1745
> URL: https://issues.apache.org/jira/browse/GEODE-1745
> Project: Geode
> Issue Type: Bug
> Reporter: nabarun
>
> This happens if the query needs to be re-evaluated because updates / index
> updates happened quite close to the query execution. During re-evaluation a
> single object is being compared with a tuple returned by CRI which does
> contain the object to be matched but along with a key. This mis-match results
> in a wrong query result.
> Fix: In CompactRangeIndex.java, while we are in the method evaluateEntry, we
> do a special check when compact map range indexes are used, and make sure the
> comparison is between the object to be searched and the first element of the
> tuple.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
