Feature/disable xcom #250
Closed
Feature/disable xcom #250
Conversation
This file contains 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.
In order to disable xcom and continue to test the functions related in stellar-et-airflow it is necessary to pass this PR.
This is the first step to disable xcom.
The idea is: We had the xcom with the values of start and end ledger.
The process in this PR is that the values of start ledger and end ledger will be in a file exported to GCS, this way the time to generate xcom will be skipped and the ledger values will be stored in a place to be used by subsequent tasks.
The test is done and it was exported successfully like the image below: