Uploaded image for project: 'CDAP'
  1. CDAP
  2. CDAP-16816

Compute profile set in a trigger does not get used

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 6.2.0, 6.3.0, 6.1.3
    • Component/s: Scheduler
    • Labels:
      None
    • Release Notes:
      Fixed schedule properties to overwrite preferences set on the application instead of the other way around. This most visibly fixed a bug where the compute profile set on a pipeline schedule or trigger would get overwritten by the profile for the pipeline.
    • Rank:
      1|i00xbb:

      Description

      It seems like the default compute profile gets used even if a different profile is set in the trigger's configuration.

      To repro set a custom compute profile for a trigger, and run the upstream pipeline.

        Attachments

          Activity

            People

            • Assignee:
              ashau Albert Shau
              Reporter:
              bhooshan Bhooshan Mogal
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: