[
https://issues.apache.org/jira/browse/FLINK-10830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-10830:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> Consider making processing time provider pluggable
> --------------------------------------------------
>
> Key: FLINK-10830
> URL: https://issues.apache.org/jira/browse/FLINK-10830
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Task
> Reporter: Andrey Zagrebin
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> At the moment, the processing time is basically implemented in a fixed way as
> System.currentTimeMillis() and not configurable by users.
> If this implementation does not fit application business logic for some
> reason there is no way for users to change it.
> Examples:
> * The timestamp provided by currentTimeMillis is not guaranteed to be
> monotonically increasing. It can jump back for a while because of possible
> periodic synchronisation of local clock with other more accurate system. It
> can be a problem for application business logic if we say that the general
> notion of time is that it always increases.
> * Hard to implement end-to-end tests because synchronisation between time in
> test and in Flink is out of control.
> We can make it configurable and let users optionally set their own factory to
> create processing time provider. All features which depend on querying
> current processing time can use this implementation. The default one can
> still stay System.currentTimeMillis().
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
