1 Answer
- Newest
- Most votes
- Most comments
1
Hi, @Alex
I tried and encountered the same problem as you.
As a workaround, you can put the parameters immediately after using the RunId of the workflow started without properties.
newRun = glue.start_workflow_run(Name = 'MyWorkflow')
updateRun = glue.put_workflow_run_properties(
Name = 'MyWorkflow',
RunId = newRun['RunId'],
RunProperties = { 'key1': 'value1'}
)
Maybe this is a boto3 issue.
I think I can report this issue...
Relevant content
- asked 2 years ago
- asked 9 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
- How can I use a Lambda function to automatically start an AWS Glue job when a crawler run completes?AWS OFFICIALUpdated 2 years ago
@Alex
I then looked into Boto3.
Apparently, the Run Properties parameter is available in the latest version of Boto3.
However, since the Boto3 version of Lambda is old, you can pass parameters with start_workflow_run by creating and using a Lambda layer that packages the latest Boto3.