[jira] [Updated] (IGNITE-15516) Add DistributedProcess chaining
[
https://issues.apache.org/jira/browse/IGNITE-15516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov updated IGNITE-15516:
---
Fix Version/s: (was: 2.15)
> Add DistributedProcess chaining
> ---
>
> Key: IGNITE-15516
> URL: https://issues.apache.org/jira/browse/IGNITE-15516
> Project: Ignite
> Issue Type: Improvement
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Labels: ise
>
> The Ignite's {{DistributedProcess}} is a cluster-wide process that
> accumulates single nodes results to finish itself. The process has of the
> following phases:
> - The initial request starts the process via discovery.
> - The coordinator accumulates all single nodes results and finish process.
> The finished message sends via discory to each node.
> To run a distributed processes afther the desired distributed process is
> finished you need to call 'start' of the next distributed process on
> coordinator. This lead to the creation of boilerplate code each time you need
> to run next.
> It is necessary to configure such thing at the processes initialization.
> {{prepareSomethingDistribProc.thenRun(rollbackDistribProc)}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-15516) Add DistributedProcess chaining
[
https://issues.apache.org/jira/browse/IGNITE-15516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-15516:
-
Labels: ise (was: )
> Add DistributedProcess chaining
> ---
>
> Key: IGNITE-15516
> URL: https://issues.apache.org/jira/browse/IGNITE-15516
> Project: Ignite
> Issue Type: Improvement
>Reporter: Maxim Muzafarov
>Priority: Major
> Labels: ise
>
> The Ignite's {{DistributedProcess}} is a cluster-wide process that
> accumulates single nodes results to finish itself. The process has of the
> following phases:
> - The initial request starts the process via discovery.
> - The coordinator accumulates all single nodes results and finish process.
> The finished message sends via discory to each node.
> To run a distributed processes afther the desired distributed process is
> finished you need to call 'start' of the next distributed process on
> coordinator. This lead to the creation of boilerplate code each time you need
> to run next.
> It is necessary to configure such thing at the processes initialization.
> {{prepareSomethingDistribProc.thenRun(rollbackDistribProc)}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-15516) Add DistributedProcess chaining
[
https://issues.apache.org/jira/browse/IGNITE-15516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-15516:
-
Fix Version/s: 2.15
> Add DistributedProcess chaining
> ---
>
> Key: IGNITE-15516
> URL: https://issues.apache.org/jira/browse/IGNITE-15516
> Project: Ignite
> Issue Type: Improvement
>Reporter: Maxim Muzafarov
>Priority: Major
> Labels: ise
> Fix For: 2.15
>
>
> The Ignite's {{DistributedProcess}} is a cluster-wide process that
> accumulates single nodes results to finish itself. The process has of the
> following phases:
> - The initial request starts the process via discovery.
> - The coordinator accumulates all single nodes results and finish process.
> The finished message sends via discory to each node.
> To run a distributed processes afther the desired distributed process is
> finished you need to call 'start' of the next distributed process on
> coordinator. This lead to the creation of boilerplate code each time you need
> to run next.
> It is necessary to configure such thing at the processes initialization.
> {{prepareSomethingDistribProc.thenRun(rollbackDistribProc)}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-15516) Add DistributedProcess chaining
[
https://issues.apache.org/jira/browse/IGNITE-15516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita updated IGNITE-15516:
-
Fix Version/s: (was: 2.13)
> Add DistributedProcess chaining
> ---
>
> Key: IGNITE-15516
> URL: https://issues.apache.org/jira/browse/IGNITE-15516
> Project: Ignite
> Issue Type: Improvement
>Reporter: Maxim Muzafarov
>Priority: Major
>
> The Ignite's {{DistributedProcess}} is a cluster-wide process that
> accumulates single nodes results to finish itself. The process has of the
> following phases:
> - The initial request starts the process via discovery.
> - The coordinator accumulates all single nodes results and finish process.
> The finished message sends via discory to each node.
> To run a distributed processes afther the desired distributed process is
> finished you need to call 'start' of the next distributed process on
> coordinator. This lead to the creation of boilerplate code each time you need
> to run next.
> It is necessary to configure such thing at the processes initialization.
> {{prepareSomethingDistribProc.thenRun(rollbackDistribProc)}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15516) Add DistributedProcess chaining
[
https://issues.apache.org/jira/browse/IGNITE-15516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amelchev Nikita updated IGNITE-15516:
-
Fix Version/s: (was: 2.12)
2.13
> Add DistributedProcess chaining
> ---
>
> Key: IGNITE-15516
> URL: https://issues.apache.org/jira/browse/IGNITE-15516
> Project: Ignite
> Issue Type: Improvement
>Reporter: Maxim Muzafarov
>Priority: Major
> Fix For: 2.13
>
>
> The Ignite's {{DistributedProcess}} is a cluster-wide process that
> accumulates single nodes results to finish itself. The process has of the
> following phases:
> - The initial request starts the process via discovery.
> - The coordinator accumulates all single nodes results and finish process.
> The finished message sends via discory to each node.
> To run a distributed processes afther the desired distributed process is
> finished you need to call 'start' of the next distributed process on
> coordinator. This lead to the creation of boilerplate code each time you need
> to run next.
> It is necessary to configure such thing at the processes initialization.
> {{prepareSomethingDistribProc.thenRun(rollbackDistribProc)}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15516) Add DistributedProcess chaining
[
https://issues.apache.org/jira/browse/IGNITE-15516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikita Safonov updated IGNITE-15516:
Fix Version/s: (was: 2.12)
2.10
> Add DistributedProcess chaining
> ---
>
> Key: IGNITE-15516
> URL: https://issues.apache.org/jira/browse/IGNITE-15516
> Project: Ignite
> Issue Type: Improvement
>Reporter: Maxim Muzafarov
>Priority: Major
> Fix For: 2.10
>
>
> The Ignite's {{DistributedProcess}} is a cluster-wide process that
> accumulates single nodes results to finish itself. The process has of the
> following phases:
> - The initial request starts the process via discovery.
> - The coordinator accumulates all single nodes results and finish process.
> The finished message sends via discory to each node.
> To run a distributed processes afther the desired distributed process is
> finished you need to call 'start' of the next distributed process on
> coordinator. This lead to the creation of boilerplate code each time you need
> to run next.
> It is necessary to configure such thing at the processes initialization.
> {{prepareSomethingDistribProc.thenRun(rollbackDistribProc)}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15516) Add DistributedProcess chaining
[
https://issues.apache.org/jira/browse/IGNITE-15516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikita Safonov updated IGNITE-15516:
Fix Version/s: (was: 2.10)
2.12
> Add DistributedProcess chaining
> ---
>
> Key: IGNITE-15516
> URL: https://issues.apache.org/jira/browse/IGNITE-15516
> Project: Ignite
> Issue Type: Improvement
>Reporter: Maxim Muzafarov
>Priority: Major
> Fix For: 2.12
>
>
> The Ignite's {{DistributedProcess}} is a cluster-wide process that
> accumulates single nodes results to finish itself. The process has of the
> following phases:
> - The initial request starts the process via discovery.
> - The coordinator accumulates all single nodes results and finish process.
> The finished message sends via discory to each node.
> To run a distributed processes afther the desired distributed process is
> finished you need to call 'start' of the next distributed process on
> coordinator. This lead to the creation of boilerplate code each time you need
> to run next.
> It is necessary to configure such thing at the processes initialization.
> {{prepareSomethingDistribProc.thenRun(rollbackDistribProc)}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15516) Add DistributedProcess chaining
[
https://issues.apache.org/jira/browse/IGNITE-15516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-15516:
-
Fix Version/s: 2.12
> Add DistributedProcess chaining
> ---
>
> Key: IGNITE-15516
> URL: https://issues.apache.org/jira/browse/IGNITE-15516
> Project: Ignite
> Issue Type: Improvement
>Reporter: Maxim Muzafarov
>Priority: Major
> Fix For: 2.12
>
>
> The Ignite's {{DistributedProcess}} is a cluster-wide process that
> accumulates single nodes results to finish itself. The process has of the
> following phases:
> - The initial request starts the process via discovery.
> - The coordinator accumulates all single nodes results and finish process.
> The finished message sends via discory to each node.
> To run a distributed processes afther the desired distributed process is
> finished you need to call 'start' of the next distributed process on
> coordinator. This lead to the creation of boilerplate code each time you need
> to run next.
> It is necessary to configure such thing at the processes initialization.
> {{prepareSomethingDistribProc.thenRun(rollbackDistribProc)}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
