[
https://issues.apache.org/jira/browse/FLINK-17178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17084607#comment-17084607
]
Jark Wu commented on FLINK-17178:
---------------------------------
[~lzljs3620320], [~ykt836], what do you think about this feature?
I'm a little concerned because ALL cache will have a big impact on external
systems and a little hack (disguise scan as lookup).
I was thinking to use changelog to support higher throughput dimension join.
> 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)
