geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Smith (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (GEODE-1985) IndexManager.needsRecalculation can miss cases where recalulation is needed
Date Mon, 07 Nov 2016 18:23:58 GMT

     [ https://issues.apache.org/jira/browse/GEODE-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dan Smith resolved GEODE-1985.
------------------------------
       Resolution: Fixed
         Assignee: Dan Smith
    Fix Version/s: 1.1.0-incubating

> IndexManager.needsRecalculation can miss cases where recalulation is needed
> ---------------------------------------------------------------------------
>
>                 Key: GEODE-1985
>                 URL: https://issues.apache.org/jira/browse/GEODE-1985
>             Project: Geode
>          Issue Type: Bug
>          Components: querying
>            Reporter: Dan Smith
>            Assignee: Dan Smith
>             Fix For: 1.1.0-incubating
>
>
> When returning query results from an index, we check IndexManager.needsRecalculation
to see if an entry might have changed while the query was in progress. 
> Unfortunately, this method can return false negatives If an entry has not yet updated
the SAFE_QUERY_TIME field.
> The SAFE_QUERY_TIME is updated in LocalRegion.updateStatsForPut. That method is called
*after* the region entry was modified. So the SAFE_QUERY_TIME could be 0, even though an entry
was modified, which will make this expression false.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message