Package software.amazon.awssdk.services.codecommit.paginators

Class DescribeMergeConflictsPublisher

  • All Implemented Interfaces:
    org.reactivestreams.Publisher<DescribeMergeConflictsResponse>, SdkPublisher<DescribeMergeConflictsResponse>
    @Generated("software.amazon.awssdk:codegen")
public class DescribeMergeConflictsPublisher
extends Object
implements SdkPublisher<DescribeMergeConflictsResponse>

    Represents the output for the CodeCommitAsyncClient.describeMergeConflictsPaginator(software.amazon.awssdk.services.codecommit.model.DescribeMergeConflictsRequest) operation which is a paginated operation. This class is a type of Publisher which can be used to provide a sequence of DescribeMergeConflictsResponse response pages as per demand from the subscriber.

    When the operation is called, an instance of this class is returned. At this point, no service calls are made yet and so there is no guarantee that the request is valid. If there are errors in your request, you will see the failures only after you start streaming the data. The subscribe method should be called as a request to start streaming data. For more info, see Publisher.subscribe(org.reactivestreams.Subscriber). Each call to the subscribe method will result in a new Subscription i.e., a new contract to stream data from the starting request.

    The following are few ways to use the response class:

    1) Using the subscribe helper method 
     
 software.amazon.awssdk.services.codecommit.paginators.DescribeMergeConflictsPublisher publisher = client.describeMergeConflictsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
    2) Using a custom subscriber 
     
 software.amazon.awssdk.services.codecommit.paginators.DescribeMergeConflictsPublisher publisher = client.describeMergeConflictsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.codecommit.model.DescribeMergeConflictsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.codecommit.model.DescribeMergeConflictsResponse response) { //... };
 });
    As the response is a publisher, it can work well with third party reactive streams implementations like RxJava2.

    Please notice that the configuration of maxMergeHunks won't limit the number of results you get with the paginator. It only limits the number of results in each page.

    Note: If you prefer to have control on service calls, use the #describeMergeConflicts(software.amazon.awssdk.services.codecommit.model.DescribeMergeConflictsRequest) operation.