[
https://issues.apache.org/jira/browse/FLINK-16781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17067297#comment-17067297
]
Jark Wu edited comment on FLINK-16781 at 3/26/20, 2:05 AM:
-----------------------------------------------------------
I don't against with this feature. But maybe [~ykt836] has some concerns.
I think one thing need to discuss is how to expose the cache configuration in
`LookupableTableSource`.
was (Author: jark):
I don't against with this feature. But maybe [~ykt836] has some concerns.
I think the problem is how to expose the cache configuration in
`LookupableTableSource`.
> add built-in cache mechanism for LookupableTableSource in lookup join
> ---------------------------------------------------------------------
>
> Key: FLINK-16781
> URL: https://issues.apache.org/jira/browse/FLINK-16781
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / API
> Reporter: Bowen Li
> Priority: Major
>
> Currently there's no built-in cache mechanism for LookupableTableSource.
> Developers have one of the following options:
> 1) build their own cache
> 2) use external cache services, like redis, memcached, etc, which Flink
> unfortunately doesn't have an out-of-box lookup function either
> 3) give up caching and bear with poor lookup performance
>
> Flink should provide a generic caching layer for all the
> LookupableTableSource to take advantage of.
>
> cc [~ykt836] [~jark] [~lzljs3620320]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
