[
https://issues.apache.org/jira/browse/FLINK-10887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16776082#comment-16776082
]
Thomas Weise commented on FLINK-10887:
--------------------------------------
There is a workaround available; I don't see it as pressing issue.
It may be good to discuss how a better solution would look like. Ideally the
user class loader would be used for RPC deserialization, not sure if that is
feasible.
If like for aggregateFunction, we would require double (de)serialization (RPC +
RpcGlobalAggregateManager), then it might be better to leave to the user
instead of assuming another layer of Java serialization.
Probably best to create a new JIRA.
> Add source watermark tracking to the JobMaster
> ----------------------------------------------
>
> Key: FLINK-10887
> URL: https://issues.apache.org/jira/browse/FLINK-10887
> Project: Flink
> Issue Type: Sub-task
> Components: JobManager
> Reporter: Jamie Grier
> Assignee: Jamie Grier
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.8.0
>
> Original Estimate: 24h
> Time Spent: 50m
> Remaining Estimate: 23h 10m
>
> We need to add a new RPC to the JobMaster such that the current watermark for
> every source sub-task can be reported and the current global minimum/maximum
> watermark can be retrieved so that each source can adjust their partition
> read rates in an attempt to keep sources roughly aligned in event time.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
