You can also link at runtime by providing the path to the dylib by adding
-Djava.library.path= in jvm options in the task manager
On Sat, Aug 24, 2019 at 9:11 PM Zhu Zhu wrote:
> Hi Abhishek,
>
> You need to export the environment variables on all the worker
> machines(not the machine to submit
Hi Abhishek,
You need to export the environment variables on all the worker machines(not
the machine to submit the job).
Alternatively, if you are submitting the job to a yarn cluster, you can use
flink conf prefix "containerized.taskmanager.env." to add environment
variables to Flink's task
Hi Miki,
Thanks for your reply. ParameterTool will only help in making the value
accessible through ParameterTool.get(). However, I need a way of accessing
the value using "System.getenv" since the underlying library uses it so.
On Sat, 24 Aug 2019 at 23:04, miki haiat wrote:
> Did you register
Hi!
I am using a library that depends on a certain environment variable set
(mandatorily). Now, I've exported this variable in my environment but
somehow it's not being read by the task manager. Following is the exception
I get when I try to run the job:
Caused by: com.example.MyCustomException:
