Synapse
  1. Synapse
  2. SYNAPSE-347

Support Dynamic Deployment of Tasks

    Details

    • Type: New Feature New Feature
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: 2.0
    • Component/s: None
    • Labels:
      None

      Description

      Tasks are not addressable via a "key". This prevents us from having tasks being added dynamically on disk and then being retrieved via a "key". An attribute called "key" should be added to the task element.

        Activity

        Hide
        Hiranya Jayathilaka added a comment -

        We often don't want to dynamically change an already running task. But if that is ever required, Synapse hot update feature can be used to achieve that. Similarly new tasks can be deployed in the runtime using hot deployment. XAR files provide a way for dynamically deploying tasks (including compiled Java code). So I think we can resolve this issue.

        Show
        Hiranya Jayathilaka added a comment - We often don't want to dynamically change an already running task. But if that is ever required, Synapse hot update feature can be used to achieve that. Similarly new tasks can be deployed in the runtime using hot deployment. XAR files provide a way for dynamically deploying tasks (including compiled Java code). So I think we can resolve this issue.
        Hide
        Rajika Kumarasiri added a comment -

        Ok, a task is a job which runs periodically according to the trigger expression. Once a job is started it'll run until it stops. It's hard to think an already started job is changed dynamically. If you need to start a new job, you'll have to stop the previous one and start a new one.
        On the other hand now synapse support hot deployment of synapse artifacts you can use that feature also to schedule a new task.
        I think we can reslove this issue.

        Rajika

        Show
        Rajika Kumarasiri added a comment - Ok, a task is a job which runs periodically according to the trigger expression. Once a job is started it'll run until it stops. It's hard to think an already started job is changed dynamically. If you need to start a new job, you'll have to stop the previous one and start a new one. On the other hand now synapse support hot deployment of synapse artifacts you can use that feature also to schedule a new task. I think we can reslove this issue. Rajika
        Hide
        Rajika Kumarasiri added a comment -

        I'd invest some time to provide a patch for this issue.

        Rajika

        Show
        Rajika Kumarasiri added a comment - I'd invest some time to provide a patch for this issue. Rajika

          People

          • Assignee:
            Hiranya Jayathilaka
            Reporter:
            Scott Hoggarth
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development