[
https://issues.apache.org/jira/browse/FLINK-14812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16978444#comment-16978444
]
Patrick Lucas commented on FLINK-14812:
---------------------------------------
Supporting some env var to augment the classpath used when running Flink sounds
totally reasonable to me, though for users who want variations on the upstream
image I still don't think it's a bad idea for them to create their own
images—especially if they are already set up to build Docker images.
In this case, a Dockerfile could be:
{code}
FROM flink:1.9
RUN ln -s ${FLINK_HOME}/opt/flink-metrics-prometheus-*.jar ${FLINK_HOME}/lib/
{code}
> Add metric libs to Flink classpath with an environment variable.
> ----------------------------------------------------------------
>
> Key: FLINK-14812
> URL: https://issues.apache.org/jira/browse/FLINK-14812
> Project: Flink
> Issue Type: New Feature
> Components: Deployment / Kubernetes, Deployment / Scripts
> Reporter: Eui Heo
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> To use the Flink metric lib you need to add it to the flink classpath. The
> documentation explains to put the jar file in the lib path.
> https://ci.apache.org/projects/flink/flink-docs-stable/monitoring/metrics.html#prometheus-orgapacheflinkmetricsprometheusprometheusreporter
> However, to deploy metric-enabled Flinks on a kubernetes cluster, we have the
> burden of creating and managing another container image. It would be more
> efficient to add the classpath using environment variables inside the
> constructFlinkClassPath function in the config.sh file.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
