Glue Job --extra-jars parameter is not persisted

0

I need to pass some extra jars to an existing Glue Job. Following the docs I have uploaded the jar to an s3 bucket and I have added the --extra-jars parameter. --extra-jars -> s3://....

I save the job and when I reload the page the config is not there anymore. If I run the job the parameter is not passed to the job !!!!

Is this a bug? Someone had the same issue? Am I doing something wrong?

profile picture
asked 9 months ago779 views
2 Answers
0

Some parameters have their own visual component, in this case when you reload it should detect the parameter and display that config as a text box "Dependent JARs path" under the advanced options.

profile pictureAWS
EXPERT
answered 9 months ago
  • I will check that but at the end of the day, the jar is not loaded.

  • "Dependent JARs path" is not filled by the --extra-jars parameter. Looks like a bug to me. It actually works the other way around. If you add a path in "Dependent JARs path" the --extra-jars param is filled and passed to the job run. If this is the way it is intended to work the docs should be updated accordingly.

0

Using Dependent JARs path works and populate the --extra-jars parameters. Directly adding the s3 path to the --extra-jars param is not persisted.

profile picture
answered 9 months ago
  • I see, must be an UI limitation, it does work fine when you create the job using other ways

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions