AWS Glue GetJob操作（Step Functions及Lambda boto3调用）未返回CodeGenConfigurationNodes问题咨询

Great question—let me break down what's going on here, because this is a common point of confusion with the Glue API documentation.

First off: this isn't a bug in boto3 or an undocumented parameter issue. The CodeGenConfigurationNodes field only exists in the GetJob response for Glue ETL Jobs that were created using Glue Studio's visual editor (the drag-and-drop interface where you build jobs with nodes like "Source", "Transform", "Sink").

If your Glue Job was created in any other way—like:

• Uploading a raw PySpark/Scala script directly via the console
• Using the AWS CLI or boto3 to create a job with a custom Command.ScriptLocation
• Cloning a script-based job instead of a visual job

Then the CodeGenConfigurationNodes field won't be present in the response, because there are no visual nodes to serialize into that field.

How to verify this: #

1. Head to the AWS Glue Console, navigate to your job, and click "Edit job".
2. If you land in a visual editor with a canvas of nodes, this job should return CodeGenConfigurationNodes when you call GetJob.
3. If you land directly in a script editor, this job won't have that field in the API response.

What if you have a visual job but still don't see the field? #

Double-check a few things:

• Make sure you're using a recent version of boto3 (run pip show boto3 to check—older versions might not handle this field correctly)
• Confirm you're calling get_job() with the exact correct JobName (case-sensitive!)
• Check the raw API response via the AWS CLI (aws glue get-job --job-name YOUR_JOB_NAME) to rule out any Lambda serialization quirks

内容的提问来源于stack exchange，提问作者Stephen Elves