-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Introduce Amazon Kinesis Analytics V2 (Managed Service for Apache Flink application) #40765
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
Conversation
vincbeck
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some nits and questions but overall I am very impressed! Very good job! There is a lot of code but everything looks good to me :)
HI @vincbeck Thank you, Really appreciate your time and looking into this PR. Apologies for the more changes in single PR , was testing around start and stop application operators thought of pushing together all these. I will make sure next time will push small block 😄 |
|
Awesome job! |
Adding Amazon Managed Service for Apache Flink . Doc, Operator, Sensor, Trigger, Waiter, Unit Test, System Test. Next will be adding Update configuration operator.
Manually tested in Breeze with.
wait_for_completion=False with a Sensor
deferrable=True.
wait_for_completion=True.
I am looking to use the DescribeApplicationOperation API to get more detailed error information when any application action is performed. Unfortunately, these calls are only available starting from Boto3 version 1.34.134, in provider config the boto3 configured >=1.30.90, but when the image gets build the version is coming 1.34.131. so in this cant use the above api.
So thought of updating it later the code to use the describe_application_operation API when the boto3 becomes >=1.34.134. Do you have any other suggestions?
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.