[jira] [Commented] (FLINK-17178) Provide "ALL" cache strategy in LookupFunction

[Lijie Wang (Jira)]

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

Lijie Wang commented on FLINK-17178:
------------------------------------

 An extra thread can load the whole table in cache initially and reload 
periodically, there is always a snapshot of the table in cache. You can get 
result directly from cache, if cache missed, we think it doesn‘t exist in 
table. 

>  Provide "ALL" cache strategy in LookupFunction
> -----------------------------------------------
>
>                 Key: FLINK-17178
>                 URL: https://issues.apache.org/jira/browse/FLINK-17178
>             Project: Flink
>          Issue Type: New Feature
>          Components: Connectors / Common
>            Reporter: Lijie Wang
>            Priority: Major
>
> We provide "ALL" cache strategy mentioned in FLINK-13252, motivation as 
> follow:
> Maintain the entire dimension table in memory to improve performance. There 
> is no IO overhead when we lookup the cached table. Reload dimension table 
> periodically for update, and we can reload asynchronously with little IO 
> delay.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)