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

Martijn Visser commented on FLINK-25409:
----------------------------------------

The JDBC connector still needs to be ported to the new Source API (FLIP-27 
https://cwiki.apache.org/confluence/display/FLINK/FLIP-27%3A+Refactor+Source+Interface)
 and Sink API (FLIP-143 
https://cwiki.apache.org/confluence/display/FLINK/FLIP-143%3A+Unified+Sink+API).
 Those interfaces also have implications to the metrics, as explained on 
FLIP-33 
https://cwiki.apache.org/confluence/display/FLINK/FLIP-33%3A+Standardize+Connector+Metrics
 and 

I can imagine refactoring the connector to these interfaces also has 
implications on this ticket. WDYT? 

> Add cache metric to LookupFunction
> ----------------------------------
>
>                 Key: FLINK-25409
>                 URL: https://issues.apache.org/jira/browse/FLINK-25409
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table SQL / Ecosystem
>            Reporter: Yuan Zhu
>            Priority: Major
>
> Since we encounter performance problem when lookup join in production env 
> frequently, adding metrics to monitor Lookup function cache is very helpful 
> to troubleshoot.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to