Uploaded image for project: 'Metadata Aggregator'
  1. Metadata Aggregator
  2. MDA-140

NPE from SplitMergeStage if a pipeline is not set

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.8.0
    • Fix Version/s: 0.9.0
    • Component/s: Pipeline
    • Labels:
      None

      Description

      If either the selectedItemPipeline or nonselectedItemPipeline are left unset, there is a run-time NullPointerException.

      If the intention had been to make this a configuration error, doInitialize should detect it, but it doesn't. Indeed it looks like the case of a missing pipeline was intended and should be treated as a null operation. This could be done either by initializing each pipeline to an empty SimplePipeline, or conditionally executing the pipelines in doExecute. The latter is probably better in some ways, but perhaps trickier as the two pipelines are executed in parallel. I suspect a lot of the other code predates the use of parallel execution.

        Attachments

          Activity

            People

            Assignee:
            ian@iay.org.uk Ian Young
            Reporter:
            ian@iay.org.uk Ian Young
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 2 hours
                2h
                Remaining:
                Time Spent - 42 minutes Remaining Estimate - 1 hour, 18 minutes
                1h 18m
                Logged:
                Time Spent - 42 minutes Remaining Estimate - 1 hour, 18 minutes
                42m