Fix KGX export #7
Merged
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
attempting partial/expand for kubernetes pod operator to ensure extraction of all edges Hardcoded total edge count to 50000, and assertion limit to 25000 and chunk size to 5000 - so it should create 2 pods I think.
moved the schedule_interval out of default_args and into the DAG constructor b/c the KubernetesPodOperator.partial() did not like that argument.
the generate_bte_operations task requires a single edges.tsv file, so I'm attempting to add a task to cat all of the generated edge*.tsv files into a single edges.tsv file.
revised log statement
nodes.tsv.gz file is now directly output to kgx-export/
fixed text_mining_agent value
updates yielded successful kgx export assertion count is still hard coded -- that is the next thing to fix.
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.
Changes made while testing KGX export