ariatosca-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ran Ziv (JIRA)" <j...@apache.org>
Subject [jira] [Created] (ARIA-239) Allow each task to define its own executor
Date Wed, 10 May 2017 11:16:04 GMT
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)

Mime
View raw message