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
Feature request: provide an option for data ls to print full file paths.
Description
If one would choose to download only a part of the file hierarchy in a data project, one can use the option --source-path-file FILE for dds data get. The expected content in FILE is a list of strings with file paths on the file server.
In order to create such a file for "cherry picking", one would first need to know the full paths on the server (given by using dds data ls --tree or in combination with --json), and then exclude all content that is not wanted for download.
Creating such a file from the current dds output is challenging (manually cut-and-paste, or try to write a parser for the tree-like output, or write a parser for the json format, then delete).
On the other hand, of we had full file paths, one could, for example, pipe the output to grep and easily get selections from the file hierarchy (and know the full file paths for dds data get).
I started trying to add the feature to data_lister.py, options.py, and __main__.py, but the recursive calls to the API etc quickly made the code too complicated for me :-)
Hi,
Feature request: provide an option for
data ls
to print full file paths.Description
If one would choose to download only a part of the file hierarchy in a data project, one can use the option
--source-path-file FILE
fordds data get
. The expected content inFILE
is a list of strings with file paths on the file server.In order to create such a file for "cherry picking", one would first need to know the full paths on the server (given by using
dds data ls --tree
or in combination with--json
), and then exclude all content that is not wanted for download.Creating such a file from the current dds output is challenging (manually cut-and-paste, or try to write a parser for the tree-like output, or write a parser for the json format, then delete).
On the other hand, of we had full file paths, one could, for example, pipe the output to
grep
and easily get selections from the file hierarchy (and know the full file paths fordds data get
).I started trying to add the feature to
data_lister.py
,options.py
, and__main__.py
, but the recursive calls to the API etc quickly made the code too complicated for me :-)Example
Current
dds data ls --tree
outputDesired usage and output
Cheers
Johan
The text was updated successfully, but these errors were encountered: