Per job symlinking

XMLWordPrintable

      The second is the pegasus.transfer.links option. Currently this is only defined at the Properties scope (ie for a whole workflow). But sometimes we want to decide whether to copy/symlink an input based on the job. E.g. a job that needs to read a small amount of data from a large file - better to symlink. Job that repeatedly reads medium sized file - better to copy. Can the scope of this be extended to at least the SiteCatalog, but perhaps to the workflow/transformation catalog as well

            Assignee:
            Karan Vahi
            Reporter:
            Ian Harry
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: