org.apache.ignite.compute

## Annotation Type ComputeTaskSpis

-     @Documented
       @Retention(value=RUNTIME)
       @Target(value=TYPE)
      public @interface ComputeTaskSpis

  This annotation allows task to specify what SPIs it wants to use. Starting with `Ignite 2.1` you can start multiple instances of `LoadBalancingSpi`, `FailoverSpi`, and `CheckpointSpi`. If you do that, you need to tell a task which SPI to use (by default it will use the fist SPI in the list).

- - ### Optional Element Summary

    Optional Elements
    Modifier and Type | Optional Element and Description
    --- | ---
    `String` | `checkpointSpi` Optional checkpoint SPI name.
    `String` | `failoverSpi` Optional failover SPI name.
    `String` | `loadBalancingSpi` Optional load balancing SPI name.

- - ### Element Detail

    - #### loadBalancingSpi

          public abstract String loadBalancingSpi

      Optional load balancing SPI name. By default, SPI name is equal to the name of the SPI class. You can change SPI name by explicitly supplying `IgniteSpi.getName()` parameter in grid configuration.
      Default:
        ""

  - - #### failoverSpi

          public abstract String failoverSpi

      Optional failover SPI name. By default, SPI name is equal to the name of the SPI class. You can change SPI name by explicitly supplying `IgniteSpi.getName()` parameter in grid configuration.
      Default:
        ""

  - - #### checkpointSpi

          public abstract String checkpointSpi

      Optional checkpoint SPI name. By default, SPI name is equal to the name of the SPI class. You can change SPI name by explicitly supplying `IgniteSpi.getName()` parameter in grid configuration.
      Default:
        ""

2020 Copyright © Apache Software Foundation
| Follow @ApacheIgnite
Ignite Database and Caching Platform | : ver. 2.9.0
Release Date | : October 15 2020