[
https://issues.apache.org/jira/browse/SPARK-47784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim resolved SPARK-47784.
----------------------------------
Fix Version/s: 4.0.0
Resolution: Fixed
Issue resolved by pull request 45960
[https://github.com/apache/spark/pull/45960]
> [State API v2] Merge TimeoutMode and TTLMode into TimeMode
> ----------------------------------------------------------
>
> Key: SPARK-47784
> URL: https://issues.apache.org/jira/browse/SPARK-47784
> Project: Spark
> Issue Type: Story
> Components: Structured Streaming
> Affects Versions: 4.0.0
> Reporter: Bhuwan Sahni
> Assignee: Bhuwan Sahni
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
>
> Currently, users need to specify the notion of time
> (ProcessingTime/EventTime) for timers and ttl separately. This allows users
> to use a single parameter.
> We do not expect users to use mix/match EventTime/ProcessingTime for timers
> and ttl in a single query because it makes hard to reason about the time
> semantics (when will timer be fired?, when will the state be evicted? etc.).
> Its simpler to stick to one notion of time throughout timers and ttl.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
