[
https://issues.apache.org/jira/browse/FLINK-14068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17328289#comment-17328289
]
Flink Jira Bot commented on FLINK-14068:
----------------------------------------
This major issue is unassigned and itself and all of its Sub-Tasks have not
been updated for 30 days. So, it has been labeled "stale-major". If this ticket
is indeed "major", please either assign yourself or give an update. Afterwards,
please remove the label. In 7 days the issue will be deprioritized.
> Use Java's Duration instead of Flink's Time
> -------------------------------------------
>
> Key: FLINK-14068
> URL: https://issues.apache.org/jira/browse/FLINK-14068
> Project: Flink
> Issue Type: Sub-task
> Components: API / DataStream, Runtime / Configuration, Runtime /
> Coordination
> Reporter: Zili Chen
> Priority: Major
> Labels: stale-major
> Fix For: 2.0.0
>
>
> As discussion in mailing list
> [here|https://lists.apache.org/x/thread.html/90ad2f1d7856cfe5bdc8f7dd678c626be96eeaeeb736e98f31660039@%3Cdev.flink.apache.org%3E]
> the community reaches a consensus that we will use Java's Duration for
> representing "time interval" instead of use Flink's Time for it.
> Specifically, Flink has two {{Time}} classes, which are
> {{org.apache.flink.api.common.time.Time}}
> {{org.apache.flink.streaming.api.windowing.time.Time}}
> the latter has been already deprecated and superseded by the former. Now we
> want to also deprecated the former and drop it in 2.0.0(we don't drop it just
> now because it is part of {{@Public}} interfaces).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
