Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Corrige validação da DAG de contratos
Contexto
A
contratos_dagdepende deraw_orgaoe é disparada ao término daorgao_dag. Por esse motivo, ela não deve possuir um agendamento próprio.A task
validaterecebia os resultados das instâncias mapeadas deingest_orgao. Quando há centenas de órgãos, o Airflow resolve cada XCom individualmente, gerando diversas requisições sequenciais ao API Server e podendo causarRuntimeErrorpor timeout.Alterações
schedule=Nonepara que acontratos_dagseja executada somente pelo trigger daorgao_dag;TriggerDagRunOperator;resultsdevalidate, evitando a resolução dos XComs das tasks mapeadas;results >> validate()para aguardar a conclusão de todas as ingestões;