[
https://issues.apache.org/jira/browse/FLINK-21415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17446497#comment-17446497
]
liwei li commented on FLINK-21415:
----------------------------------
I double-checked the code and found that cache is not enabled by default unless
the user sets the {{lookup.cache.max-rows}} and {{{}lookup.cache.ttl{}}}. so is
it necessary to add a new switch table option? Or give max-rows and ttl a
default value when the optionto turnned on? [~jark]
> JDBC connector should support to disable caching missing key
> ------------------------------------------------------------
>
> Key: FLINK-21415
> URL: https://issues.apache.org/jira/browse/FLINK-21415
> Project: Flink
> Issue Type: New Feature
> Components: Connectors / JDBC, Table SQL / Ecosystem
> Affects Versions: 1.12.1
> Reporter: Shuai Xia
> Assignee: liwei li
> Priority: Minor
> Labels: auto-deprioritized-major, pull-request-available
>
> JDBC does not query data, and the cache will store an ArrayList without data.
> We should add size judgment.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
