[teiid-issues] [JBoss JIRA] (TEIID-3359) Allow more control over odata layer caching

[Ramesh Reddy (JIRA)]

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

Ramesh Reddy resolved TEIID-3359.
---------------------------------
        Labels: Alpha1  (was: )
    Resolution: Done


For the OData that are paged, 
1) Now in their "skipToken" will include the "sessionid" from the initial connection they used to retrieve the results. 
2) The query string will be appended with a comment that contains sessionid. By doing this if there are two users who issue a same query, but are expecting different results, will not be served from the stale cache.

I do think we need a way explicitly expire cache, when scrolling through the page is came to a end, or a resultset with less than BATCH_COUNT amount of results. This way Teiid can proactively clean/flush them up?

> Allow more control over odata layer caching
> -------------------------------------------
>
>                 Key: TEIID-3359
>                 URL: https://issues.jboss.org/browse/TEIID-3359
>             Project: Teiid
>          Issue Type: Enhancement
>          Components: OData
>    Affects Versions: 8.7
>            Reporter: Steven Hawkins
>            Assignee: Ramesh Reddy
>              Labels: Alpha1
>             Fix For: 8.11
>
>
> The caching is always performed at a user level and for each query.  Consumers may need to localize the caching affect only to paging results and  scope only to that interaction, rather than for all users.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)