[ 
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 stale-minor  (was: 
auto-deprioritized-major)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issues has been marked as 
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated 
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is 
still Minor, please either assign yourself or give an update. Afterwards, 
please remove the label or in 7 days the issue will be deprioritized.


> 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: Minor
>              Labels: auto-deprioritized-major, stale-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)

Reply via email to