[
https://issues.apache.org/jira/browse/FLINK-11139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16727100#comment-16727100
]
Fabian Hueske commented on FLINK-11139:
---------------------------------------
Without knowing the details about the join that is used, I cannot comment.
Just one thing to consider: TTL also has a memory footprint. It adds a long
timestamp to each state entry, i.e., one long per key.
> stream non window join support state ttl
> ----------------------------------------
>
> Key: FLINK-11139
> URL: https://issues.apache.org/jira/browse/FLINK-11139
> Project: Flink
> Issue Type: Improvement
> Components: Table API & SQL
> Affects Versions: 1.7.0
> Reporter: zhaoshijie
> Assignee: zhaoshijie
> Priority: Major
>
> stream non window join function use timer to delete expired data，it is ok for
> small amount of data or short expiration time，but it will be OOM（too many
> timer）on taskManger when there is a long expiration time and a large
> amount of data。In fact, table module other state function has same problem，I
> would like to contribute to fix it。
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
