Details

      Description

      The provenance database should be able to store information about the looping of a service invocation. Information about the looping should be viewable in the list view of the workflow run and in the details about a service iteration.

      Relates to T2-1211 - so if you do one retries first, loops should be very similar. (In a way it is a special kind of retry)

      Solution:
      Modify provenance database to record individual loops, including their inputs and outputs and processing times.
      Modify query to always use last outputs and first inputs
      Modify query and respons to show all loops (with their individual inputs and outputs)
      Modify GUI to show all loops

      Testing:
      Create test workflows with various loop conditions, both with and without port feedback
      Assert lookup query uses LAST loop outputs and FIRST loop inputs, unless inclusion of each loop is included
      Assert provenance still works when there is no looping

        Issue Links

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              Stian Soiland-Reyes
              Reporter:
              Stian Soiland-Reyes
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:

                Time Tracking

                Estimated:
                Original Estimate - 1 day
                1d
                Remaining:
                Remaining Estimate - 1 day
                1d
                Logged:
                Time Spent - Not Specified
                Not Specified