-
Notifications
You must be signed in to change notification settings - Fork 26
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
Implement Async for native Spark Operators #119
Comments
If we have too many issues with it, we can park it for now, or use LivyOperator as an alternative to submit Spark jobs |
We've got the local connection working for the SparkSubmitOperator yesterday post further analysis. I think this story is unblocked for now @sunank200 , @bharanidharan14 - please comment. |
Yes, |
on 7-03-2022 and 21-03-2022 Successfully Installed spark in the airflow worker to run the spark-submit job and Created the spark cluster container tried running the sample spark job via airflow worker, I was facing some issues with container resource allocation issue. |
Working on implementing Spark submit operator async |
Trying to debug the issue right now and blocked on this. Submit job runs fine for me though. |
@sunank200 lets stop further effort on SparkSQLOperator and you can start on LivyOperator |
SparkSubmitOperator
|
Added the changes to submit the spark submit job in execute method and getting the status from trigger |
Below operators are on hold due to connectivity issue between airflow worker container and EMR Spark
|
Implement async versions for the following operators(Aligned on descending order of priority):
SparkSubmitOperator
- @bharanidharan14SparkSqlOperator
- @sunank200SparkJDBCOperator
LivyOperator
- @sunank200SparkKubernetesOperator
Acceptance Criteria:
The text was updated successfully, but these errors were encountered: