You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ariatosca.apache.org by "Ran Ziv (JIRA)" <ji...@apache.org> on 2017/05/10 11:16:04 UTC

[jira] [Created] (ARIA-239) Allow each task to define its own executor

Ran Ziv created ARIA-239:
----------------------------

             Summary: Allow each task to define its own executor
                 Key: ARIA-239
                 URL: https://issues.apache.org/jira/browse/ARIA-239
             Project: AriaTosca
          Issue Type: Story
            Reporter: Ran Ziv
            Priority: Trivial


Currently, the task executor granularity is at the execution level - all tasks use the same executor (except for stub tasks, but that's a separate topic).

It should be made possible for users to define (possibly in the service-template, workflow, or both) which executor they'd like to execute a specific operation with.

For example, the execution plugin, which is built-in, can use the ThreadExecutor (in theory; it might actually run into concurrency issues since Fabric's environment is not thread-safe) even if operations that use custom plugins can't, and thereby increase performance etc.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)