public class BatchAbandon
extends java.lang.Object
Modifier and Type | Method and Description |
---|---|
void |
batchAbandon(BatchUpdate.Factory updateFactory,
Project.NameKey project,
CurrentUser user,
java.util.Collection<ChangeData> changes) |
void |
batchAbandon(BatchUpdate.Factory updateFactory,
Project.NameKey project,
CurrentUser user,
java.util.Collection<ChangeData> changes,
java.lang.String msgTxt) |
void |
batchAbandon(BatchUpdate.Factory updateFactory,
Project.NameKey project,
CurrentUser user,
java.util.Collection<ChangeData> changes,
java.lang.String msgTxt,
NotifyHandling notifyHandling,
com.google.common.collect.ListMultimap<RecipientType,Account.Id> accountsToNotify)
If an extension has more than one changes to abandon that belong to the same project, they
should use the batch instead of abandoning one by one.
|
public void batchAbandon(BatchUpdate.Factory updateFactory, Project.NameKey project, CurrentUser user, java.util.Collection<ChangeData> changes, java.lang.String msgTxt, NotifyHandling notifyHandling, com.google.common.collect.ListMultimap<RecipientType,Account.Id> accountsToNotify) throws RestApiException, UpdateException
It's the caller's responsibility to ensure that all jobs inside the same batch have the matching project from its ChangeData. Violations will result in a ResourceConflictException.
RestApiException
UpdateException
public void batchAbandon(BatchUpdate.Factory updateFactory, Project.NameKey project, CurrentUser user, java.util.Collection<ChangeData> changes, java.lang.String msgTxt) throws RestApiException, UpdateException
RestApiException
UpdateException
public void batchAbandon(BatchUpdate.Factory updateFactory, Project.NameKey project, CurrentUser user, java.util.Collection<ChangeData> changes) throws RestApiException, UpdateException
RestApiException
UpdateException