[
https://issues.apache.org/jira/browse/FLINK-14812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16978315#comment-16978315
]
Ufuk Celebi commented on FLINK-14812:
-------------------------------------
[~elanv] I think your work around with adding single JARs to
{{HADOOP_CLASSPATH}} is the best option currently.
I think the question for this ticket is independent of metrics and Kubernetes.
The general question is whether we want to add an Hadoop-independent
environment variable such as {{CLASSPATH_ADDITIONAL_JARS}} that we document and
commit to maintain for our start up scripts.
Personally, I would find this beneficial in the standalone job use case.
[~plucas] What do you think?
---
I'm not sure who in the Flink community has good insight on the scripts and can
help us make a decision here. [~aljoscha] or [~chesnay] maybe?
> 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)
