[ https://issues.apache.org/jira/browse/AIRAVATA-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcus Christie updated AIRAVATA-3282: -------------------------------------- Description: The log files are typically at the top level Airavata workdir and we have now a way to get them using an output field in the app interface. If the file is buried in some sub-directories below it is not possible. One may want to use the wildcards such as {{"*/*/*.log"}} in such cases. \*\* Also it may be needed to preserve the hierarchy of the directories when downloaded to potentially get other data or use it in an alternate context. (was: The log files are typically at the top level Airavata workdir and we have now a way to get them using an output field in the app interface. If the file is buried in some sub-directories below it is not possible. One may want to use the wildcards such as {{"*/*/*.log"}} in such cases. ** Also it may be needed to preserve the hierarchy of the directories when downloaded to potentially get other data or use it in an alternate context.) > To get output files not at a top level and preserve the hierarchy potentially > ----------------------------------------------------------------------------- > > Key: AIRAVATA-3282 > URL: https://issues.apache.org/jira/browse/AIRAVATA-3282 > Project: Airavata > Issue Type: New Feature > Reporter: Sudhakar Pamidighantam > Assignee: Dimuthu Upeksha > Priority: Major > > The log files are typically at the top level Airavata workdir and we have now > a way to get them using an output field in the app interface. If the file is > buried in some sub-directories below it is not possible. One may want to use > the wildcards such as {{"*/*/*.log"}} in such cases. \*\* Also it may be > needed to preserve the hierarchy of the directories when downloaded to > potentially get other data or use it in an alternate context. -- This message was sent by Atlassian Jira (v8.3.4#803005)