[
https://issues.apache.org/jira/browse/FLINK-6491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004896#comment-16004896
]
ASF GitHub Bot commented on FLINK-6491:
---------------------------------------
Github user fhueske commented on a diff in the pull request:
https://github.com/apache/flink/pull/3863#discussion_r115779043
--- Diff:
flink-libraries/flink-table/src/test/scala/org/apache/flink/table/runtime/harness/OverWindowHarnessTest.scala
---
@@ -220,15 +74,19 @@ class OverWindowHarnessTest extends HarnessTestBase{
testHarness.processElement(new StreamRecord(
CRow(Row.of(2: JInt, 0L: JLong, 0: JInt, "bbb", 30L: JLong), true),
1))
- testHarness.setProcessingTime(2)
+ // trigger cleanup timer and register cleanup timer with 6001
+ testHarness.setProcessingTime(3001)
testHarness.processElement(new StreamRecord(
CRow(Row.of(1: JInt, 11L: JLong, 1: JInt, "aaa", 7L: JLong), true),
2))
testHarness.processElement(new StreamRecord(
CRow(Row.of(1: JInt, 11L: JLong, 1: JInt, "aaa", 8L: JLong), true),
2))
testHarness.processElement(new StreamRecord(
CRow(Row.of(1: JInt, 11L: JLong, 1: JInt, "aaa", 9L: JLong), true),
2))
+
+ // using historical data and register cleanup timer with 9000
--- End diff --
what do you mean by historical data?
> Add QueryConfig to specify state retention time for streaming queries
> ---------------------------------------------------------------------
>
> Key: FLINK-6491
> URL: https://issues.apache.org/jira/browse/FLINK-6491
> Project: Flink
> Issue Type: Bug
> Components: Table API & SQL
> Affects Versions: 1.3.0
> Reporter: Fabian Hueske
> Assignee: sunjincheng
> Priority: Critical
>
> By now we have a couple of streaming operators (group-windows, over-windows,
> non-windowed aggregations) that require operator state. Since state is not
> automatically cleaned-up by Flink, we need to add a mechanism to configure a
> state retention time.
> If configured, a query will retain state for a specified period of state
> inactivity. If state is not accessed within this period of time, it will be
> cleared. I propose to add two parameters for this, a min and a max retention
> time. The min retention time specifies the earliest time and the max
> retention time the latest time when state is cleared. The reasoning for
> having two parameters is that we can avoid to register many timers if we have
> more freedom when to discard state.
> This issue also introduces a QueryConfig object which can be passed to a
> streaming query, when it is emitted to a TableSink or converted to a
> DataStream (append or retraction).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
