[ 
https://issues.apache.org/jira/browse/FLINK-10887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16713143#comment-16713143
 ] 

ASF GitHub Bot commented on FLINK-10887:
----------------------------------------

jgrier commented on issue #7099: [FLINK-10887] [jobmaster] Add source watermark 
tracking to the JobMaster
URL: https://github.com/apache/flink/pull/7099#issuecomment-445316366
 
 
   > Can we always assume that the user-jar/class loader will be available 
where the `AggregateFunction` is needed? If yes, I think this is a nice 
approach! (We can probably use concrete types in the interface, though)
   
   @aljoscha I'm actually not sure if the user code classloader is available 
from the JobMaster but I would think that's reasonable since there's a 1:1 
relationship between the JobMaster and a single job.
   
   WRT concrete types in the RPC interface I'm not sure what you're thinking 
there.  The concrete types are not known in this approach.  The types are up to 
the user/client and can be different for each named aggregate.
   
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> 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
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> 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)

Reply via email to