[
https://issues.apache.org/jira/browse/FLINK-34001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17804090#comment-17804090
]
xuyang commented on FLINK-34001:
--------------------------------
[~luca.yang] I guess what you want is that all( or part) data in dimension
table can be cached in memory, and then reduce the pressure on frequent queries
to the database? You can ref
[lookup.cache|https://nightlies.apache.org/flink/flink-docs-master/docs/connectors/table/jdbc/#lookup-cache-1]
> Fix ambiguous document description towards the default value for configuring
> operator-level state TTL
> -----------------------------------------------------------------------------------------------------
>
> Key: FLINK-34001
> URL: https://issues.apache.org/jira/browse/FLINK-34001
> Project: Flink
> Issue Type: Improvement
> Components: Documentation, Table SQL / API
> Affects Versions: 1.18.0
> Reporter: yong yang
> Assignee: Jane Chan
> Priority: Major
>
> doc:
> https://nightlies.apache.org/flink/flink-docs-release-1.18/docs/dev/table/concepts/overview/#idle-state-retention-time
> The current TTL value for both left and right side is {{{}"0 ms"{}}}, which
> means the state retention is not enabled.
>
> but i test find :
> The current TTL value for both left and right side is {{{}"0 ms"{}}}, which
> means the state is permanence keep!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
