You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I would like to be able to run a KGX transform where JSON Lines files are exported as a singular tar.gz file.
At this moment if run monarch-ingest and cat-merge to get some TSVs and then run a KGX transform command like
poetry run kgx transform --input-format tsv --input-compression tar.gz --output output/mokg-jsonl --output-format jsonl --output-compression tar.gz output/mokg.tar.gz
The "output-compression" parameter will end up ignored and the files will be outputted from this command will be two files; output/mokg-jsonl_nodes.jsonl.tar.gz and output/mokg-json_edges.jsonl.tar.gz.
Describe the solution you'd like
Allow the JSONL writer to be able to handle tar.gz as an output compression.
Describe alternatives you've considered
Make JSONL writer fail when passing in invalid compression parameter.
Additional context
Code pointing to TSV Sink Compression code right now.
Is your feature request related to a problem? Please describe.
I would like to be able to run a KGX transform where JSON Lines files are exported as a singular tar.gz file.
At this moment if run monarch-ingest and cat-merge to get some TSVs and then run a KGX transform command like
Describe the solution you'd like
Allow the JSONL writer to be able to handle tar.gz as an output compression.
Describe alternatives you've considered
Make JSONL writer fail when passing in invalid compression parameter.
Additional context
Code pointing to TSV Sink Compression code right now.
kgx/kgx/sink/tsv_sink.py
Lines 138 to 149 in f5c8ab9
Code pointing to JSON Lines Sink Compression code right now.
kgx/kgx/sink/jsonl_sink.py
Lines 49 to 55 in f5c8ab9
Notice that JSONL doesn't support tar.gz compression format.
kgx/kgx/sink/jsonl_sink.py
Lines 23 to 24 in f5c8ab9
The text was updated successfully, but these errors were encountered: