This is an optional parameter that can make a queued load request contingent on the successful completion of one or more previous jobs in the queue.Neptune can queue up as many as 64 load requests at a time, if their
queueRequest parameters are set to
"TRUE". The
dependencies parameter lets you make execution of such a queued request dependent on the successful completion of one or more specified previous requests in the queue.For example, if load
Job-A and
Job-B are independent of each other, but load
Job-C needs
Job-A and
Job-B to be finished before it begins, proceed as follows:
- Submit load-job-A and load-job-B one after another in any order, and save their load-ids.
- Submit load-job-C with the load-ids of the two jobs in its dependencies field:
Because of the
dependencies parameter, the bulk loader will not start
Job-C until
Job-A and
Job-B have completed successfully. If either one of them fails, Job-C will not be executed, and its status will be set to
LOAD_FAILED_BECAUSE_DEPENDENCY_NOT_SATISFIED.You can set up multiple levels of dependency in this way, so that the failure of one job will cause all requests that are directly or indirectly dependent on it to be cancelled. Starting with version 4 of the SDK this property will default to null. If no data for this property is returned from the service the property will also be null. This was changed to improve performance and allow the SDK and caller to distinguish between a property not set or a property being empty to clear out a value. To retain the previous SDK behavior set the AWSConfigs.InitializeCollections static property to true.