[jira] [Commented] (LENS-303) Cache latest partition for facts and serve latestdate api from cache

["Amareshwari Sriramadasu (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LENS-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14315879#comment-14315879 ] 

Amareshwari Sriramadasu commented on LENS-303:
----------------------------------------------

Since we already cache Fact tables, these values can be cached in Fact table directly.

* If Add partition api is adding latest, it should update cache along with metastore.
* If Drop partition api is dropping latest, it should update cache along with metastore.
* On server start, irrespective of add/drop partition api, the latest value should be available in cache.

> Cache latest partition for facts and serve latestdate api from cache
> --------------------------------------------------------------------
>
>                 Key: LENS-303
>                 URL: https://issues.apache.org/jira/browse/LENS-303
>             Project: Apache Lens
>          Issue Type: Improvement
>          Components: cube, server
>            Reporter: Amareshwari Sriramadasu
>             Fix For: 2.1
>
>
> We can cache latest partition for each fact in the table. We will have cached values of latest partition for each storage, for each time partition column.
> I think we might need latest value for each update period as well.
> Once we have the values in Fact table, the latest date api can serve the value directly from cache



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