-
Notifications
You must be signed in to change notification settings - Fork 14.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add deferrable support to LambdaInvokeFunctionOperator
#40307
Comments
LambdaInvokeFunctionOperator
LambdaInvokeFunctionOperator
Indeed, that'd be a cool add-on! |
Happy to look Into this: 😀 |
Assigned |
@gopidesupavan, have you started to work on it? Do you have any lead? I am asking this because I recall now there is no Lambda API to fetch status of a given execution. Which then makes this task impossible. Any pooling mechanism on a Lambda execution is purely impossible because there is no API to retrieve status |
But we do have |
|
But if @gopidesupavan is interested in a similar issue, there is this issue: #40207. It seems the operator |
Hi @eladkal @vincbeck , actually i was started this task yesterday, agreed what you said is correct. No option to get the execution status of lambda execution. What i am thinking is invoking lambda with async with deferable from the trigger. I thinking of some cases useful, where the lambda execution takes more time say (more than 5min) and InvocationType=RequestResponse. so in this case the trigger can listen on the response from the lambda?. This is trigger logic am planning:
Do you think something that usable? or is this approach not required? |
|
As mentioned in #40425, this is not possible because AWS Lambda does not provide an API to retrieve status of an execution. Without this capability, it is not possible to make this operator deferrable |
Body
#33327 added deferrable option to
LambdaCreateFunctionOperator
we should have similar functionality inLambdaInvokeFunctionOperator
Committer
The text was updated successfully, but these errors were encountered: