[teiid-issues] [JBoss JIRA] (TEIID-2622) Data/plan modification check is not granular enough

[Steven Hawkins (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins resolved TEIID-2622.
-----------------------------------

    Resolution: Done


changed to simply invalid when the modification time matches the entry time.  other methods such as using a version number are not as cluster friendly (although we're assuming low clock skew for the timestamping to be cluster friendly).  It may still be beneficial to use versioning at some point.

This may introduce situations especially on systems with poor time resolution of being too cautious about using cache entries - but sense we typical caching either plan is typically used for operations lasting longer than typical time resolutions this seems fine for now.
                
> Data/plan modification check is not granular enough
> ---------------------------------------------------
>
>                 Key: TEIID-2622
>                 URL: https://issues.jboss.org/browse/TEIID-2622
>             Project: Teiid
>          Issue Type: Quality Risk
>          Components: Query Engine
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 8.4.1, 8.5
>
>
> The use of milliseconds will cause some situations (such as in the TestAsynch alter test) where modifications do not seem to be honored.

--
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