Uploaded image for project: 'Pegasus'
  1. Pegasus
  2. PM-512

Do tools really need a pegasus prefix when they reside in the pegasus namespace?

XMLWordPrintable

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major Major
    • master, 4.0
    • Affects Version/s: master
    • Component/s: Pegasus Planner
    • None

      [1] java.lang.RuntimeException: Could not find entry in tc for lfn pegasus::pegasus-transfer at site fg-alamo at edu.isi.pegasus.planner.transfer.implementation.AbstractMultipleFTPerXFERJob.createTransferJob(AbstractMultipleFTPerXFERJob.java:139)

      I'm not worried about the actual error in this report, but about the fact that it looks for pegasus::pegasus-transfer. I think that is overkill, and when talking in abstract transformation terms, the physical "pegasus-" prefix should be dropped in favor of the "pegasus" namespace. Thus, it should for pegasus::transfer and not pegasus::pegasus-transfer.

            Assignee:
            vahi Karan Vahi
            Reporter:
            voeckler Jens Voeckler
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: