[
https://issues.apache.org/jira/browse/FLINK-17178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17085480#comment-17085480
]
Jingsong Lee commented on FLINK-17178:
--------------------------------------
Although it doesn't look very elegant, I think there is a real need.
And this is a very simple implementation and usage. Users can easily understand
it. It can auto-fresh periodically and achieve high-performance effects and
avoid frequent access to external dimension tables.
Use changelog? Maybe users need a lot of effort to understand..
I know it is a need but no good suggestion for api.
> 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.
> The cache needs to be reloaded periodically for update。
> Limitations：
> 1. It's suitable for scenario that users don't care the lateness so much,
> periodically updating can satisfy them.
> 2. The “ALL” cache needs more memory, so it's suitable for small dimension
> table.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
