Interface NeptuneAsyncClient

All Superinterfaces:
AutoCloseable, AwsClient, SdkAutoCloseable, SdkClient
@Generated("software.amazon.awssdk:codegen") @ThreadSafe public interface NeptuneAsyncClient extends AwsClient
Service client for accessing Amazon Neptune asynchronously. This can be created using the static builder() method.The asynchronous client performs non-blocking I/O when configured with any SdkAsyncHttpClient supported in the SDK. However, full non-blocking is not guaranteed as the async client may perform blocking calls in some cases such as credentials retrieval and endpoint discovery as part of the async API call. Amazon Neptune

Amazon Neptune is a fast, reliable, fully-managed graph database service that makes it easy to build and run applications that work with highly connected datasets. The core of Amazon Neptune is a purpose-built, high-performance graph database engine optimized for storing billions of relationships and querying the graph with milliseconds latency. Amazon Neptune supports popular graph models Property Graph and W3C's RDF, and their respective query languages Apache TinkerPop Gremlin and SPARQL, allowing you to easily build queries that efficiently navigate highly connected datasets. Neptune powers graph use cases such as recommendation engines, fraud detection, knowledge graphs, drug discovery, and network security.

This interface reference for Amazon Neptune contains documentation for a programming or command line interface you can use to manage Amazon Neptune. Note that Amazon Neptune is asynchronous, which means that some interfaces might require techniques such as polling or callback functions to determine when a command has been applied. In this reference, the parameter descriptions indicate whether a command is applied immediately, on the next instance reboot, or during the maintenance window. The reference structure is as follows, and we list following some related topics from the user guide.

  • Field Details

  • Method Details

    • addRoleToDBCluster

      default CompletableFuture<AddRoleToDbClusterResponse> addRoleToDBCluster(AddRoleToDbClusterRequest addRoleToDbClusterRequest)

      Associates an Identity and Access Management (IAM) role with an Neptune DB cluster.

      Parameters:
      addRoleToDbClusterRequest -
      Returns:
      A Java Future containing the result of the AddRoleToDBCluster operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • DbClusterRoleAlreadyExistsException The specified IAM role Amazon Resource Name (ARN) is already associated with the specified DB cluster.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • DbClusterRoleQuotaExceededException You have exceeded the maximum number of IAM roles that can be associated with the specified DB cluster.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • addRoleToDBCluster

      default CompletableFuture<AddRoleToDbClusterResponse> addRoleToDBCluster(Consumer<AddRoleToDbClusterRequest.Builder> addRoleToDbClusterRequest)

      Associates an Identity and Access Management (IAM) role with an Neptune DB cluster.


      This is a convenience which creates an instance of the AddRoleToDbClusterRequest.Builder avoiding the need to create one manually via AddRoleToDbClusterRequest.builder()

      Parameters:
      addRoleToDbClusterRequest - A Consumer that will call methods on AddRoleToDbClusterRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the AddRoleToDBCluster operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • DbClusterRoleAlreadyExistsException The specified IAM role Amazon Resource Name (ARN) is already associated with the specified DB cluster.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • DbClusterRoleQuotaExceededException You have exceeded the maximum number of IAM roles that can be associated with the specified DB cluster.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • addSourceIdentifierToSubscription

      default CompletableFuture<AddSourceIdentifierToSubscriptionResponse> addSourceIdentifierToSubscription(AddSourceIdentifierToSubscriptionRequest addSourceIdentifierToSubscriptionRequest)

      Adds a source identifier to an existing event notification subscription.

      Parameters:
      addSourceIdentifierToSubscriptionRequest -
      Returns:
      A Java Future containing the result of the AddSourceIdentifierToSubscription operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SubscriptionNotFoundException The designated subscription could not be found.
      • SourceNotFoundException The source could not be found.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • addSourceIdentifierToSubscription

      default CompletableFuture<AddSourceIdentifierToSubscriptionResponse> addSourceIdentifierToSubscription(Consumer<AddSourceIdentifierToSubscriptionRequest.Builder> addSourceIdentifierToSubscriptionRequest)

      Adds a source identifier to an existing event notification subscription.


      This is a convenience which creates an instance of the AddSourceIdentifierToSubscriptionRequest.Builder avoiding the need to create one manually via AddSourceIdentifierToSubscriptionRequest.builder()

      Parameters:
      addSourceIdentifierToSubscriptionRequest - A Consumer that will call methods on AddSourceIdentifierToSubscriptionRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the AddSourceIdentifierToSubscription operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SubscriptionNotFoundException The designated subscription could not be found.
      • SourceNotFoundException The source could not be found.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • addTagsToResource

      default CompletableFuture<AddTagsToResourceResponse> addTagsToResource(AddTagsToResourceRequest addTagsToResourceRequest)

      Adds metadata tags to an Amazon Neptune resource. These tags can also be used with cost allocation reporting to track cost associated with Amazon Neptune resources, or used in a Condition statement in an IAM policy for Amazon Neptune.

      Parameters:
      addTagsToResourceRequest -
      Returns:
      A Java Future containing the result of the AddTagsToResource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbInstanceNotFoundException DBInstanceIdentifier does not refer to an existing DB instance.
      • DbSnapshotNotFoundException DBSnapshotIdentifier does not refer to an existing DB snapshot.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • addTagsToResource

      default CompletableFuture<AddTagsToResourceResponse> addTagsToResource(Consumer<AddTagsToResourceRequest.Builder> addTagsToResourceRequest)

      Adds metadata tags to an Amazon Neptune resource. These tags can also be used with cost allocation reporting to track cost associated with Amazon Neptune resources, or used in a Condition statement in an IAM policy for Amazon Neptune.


      This is a convenience which creates an instance of the AddTagsToResourceRequest.Builder avoiding the need to create one manually via AddTagsToResourceRequest.builder()

      Parameters:
      addTagsToResourceRequest - A Consumer that will call methods on AddTagsToResourceRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the AddTagsToResource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbInstanceNotFoundException DBInstanceIdentifier does not refer to an existing DB instance.
      • DbSnapshotNotFoundException DBSnapshotIdentifier does not refer to an existing DB snapshot.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • applyPendingMaintenanceAction

      default CompletableFuture<ApplyPendingMaintenanceActionResponse> applyPendingMaintenanceAction(ApplyPendingMaintenanceActionRequest applyPendingMaintenanceActionRequest)

      Applies a pending maintenance action to a resource (for example, to a DB instance).

      Parameters:
      applyPendingMaintenanceActionRequest -
      Returns:
      A Java Future containing the result of the ApplyPendingMaintenanceAction operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ResourceNotFoundException The specified resource ID was not found.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • applyPendingMaintenanceAction

      default CompletableFuture<ApplyPendingMaintenanceActionResponse> applyPendingMaintenanceAction(Consumer<ApplyPendingMaintenanceActionRequest.Builder> applyPendingMaintenanceActionRequest)

      Applies a pending maintenance action to a resource (for example, to a DB instance).


      This is a convenience which creates an instance of the ApplyPendingMaintenanceActionRequest.Builder avoiding the need to create one manually via ApplyPendingMaintenanceActionRequest.builder()

      Parameters:
      applyPendingMaintenanceActionRequest - A Consumer that will call methods on ApplyPendingMaintenanceActionRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ApplyPendingMaintenanceAction operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ResourceNotFoundException The specified resource ID was not found.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • copyDBClusterParameterGroup

      default CompletableFuture<CopyDbClusterParameterGroupResponse> copyDBClusterParameterGroup(CopyDbClusterParameterGroupRequest copyDbClusterParameterGroupRequest)

      Copies the specified DB cluster parameter group.

      Parameters:
      copyDbClusterParameterGroupRequest -
      Returns:
      A Java Future containing the result of the CopyDBClusterParameterGroup operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • DbParameterGroupQuotaExceededException Request would result in user exceeding the allowed number of DB parameter groups.
      • DbParameterGroupAlreadyExistsException A DB parameter group with the same name exists.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • copyDBClusterParameterGroup

      default CompletableFuture<CopyDbClusterParameterGroupResponse> copyDBClusterParameterGroup(Consumer<CopyDbClusterParameterGroupRequest.Builder> copyDbClusterParameterGroupRequest)

      Copies the specified DB cluster parameter group.


      This is a convenience which creates an instance of the CopyDbClusterParameterGroupRequest.Builder avoiding the need to create one manually via CopyDbClusterParameterGroupRequest.builder()

      Parameters:
      copyDbClusterParameterGroupRequest - A Consumer that will call methods on CopyDbClusterParameterGroupRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the CopyDBClusterParameterGroup operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • DbParameterGroupQuotaExceededException Request would result in user exceeding the allowed number of DB parameter groups.
      • DbParameterGroupAlreadyExistsException A DB parameter group with the same name exists.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • copyDBClusterSnapshot

      default CompletableFuture<CopyDbClusterSnapshotResponse> copyDBClusterSnapshot(CopyDbClusterSnapshotRequest copyDbClusterSnapshotRequest)

      Copies a snapshot of a DB cluster.

      To copy a DB cluster snapshot from a shared manual DB cluster snapshot, SourceDBClusterSnapshotIdentifier must be the Amazon Resource Name (ARN) of the shared DB cluster snapshot.

      Parameters:
      copyDbClusterSnapshotRequest -
      Returns:
      A Java Future containing the result of the CopyDBClusterSnapshot operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterSnapshotAlreadyExistsException User already has a DB cluster snapshot with the given identifier.
      • DbClusterSnapshotNotFoundException DBClusterSnapshotIdentifier does not refer to an existing DB cluster snapshot.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • InvalidDbClusterSnapshotStateException The supplied value is not a valid DB cluster snapshot state.
      • SnapshotQuotaExceededException Request would result in user exceeding the allowed number of DB snapshots.
      • KmsKeyNotAccessibleException Error accessing KMS key.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • copyDBClusterSnapshot

      default CompletableFuture<CopyDbClusterSnapshotResponse> copyDBClusterSnapshot(Consumer<CopyDbClusterSnapshotRequest.Builder> copyDbClusterSnapshotRequest)

      Copies a snapshot of a DB cluster.

      To copy a DB cluster snapshot from a shared manual DB cluster snapshot, SourceDBClusterSnapshotIdentifier must be the Amazon Resource Name (ARN) of the shared DB cluster snapshot.


      This is a convenience which creates an instance of the CopyDbClusterSnapshotRequest.Builder avoiding the need to create one manually via CopyDbClusterSnapshotRequest.builder()

      Parameters:
      copyDbClusterSnapshotRequest - A Consumer that will call methods on CopyDbClusterSnapshotRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the CopyDBClusterSnapshot operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterSnapshotAlreadyExistsException User already has a DB cluster snapshot with the given identifier.
      • DbClusterSnapshotNotFoundException DBClusterSnapshotIdentifier does not refer to an existing DB cluster snapshot.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • InvalidDbClusterSnapshotStateException The supplied value is not a valid DB cluster snapshot state.
      • SnapshotQuotaExceededException Request would result in user exceeding the allowed number of DB snapshots.
      • KmsKeyNotAccessibleException Error accessing KMS key.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • copyDBParameterGroup

      default CompletableFuture<CopyDbParameterGroupResponse> copyDBParameterGroup(CopyDbParameterGroupRequest copyDbParameterGroupRequest)

      Copies the specified DB parameter group.

      Parameters:
      copyDbParameterGroupRequest -
      Returns:
      A Java Future containing the result of the CopyDBParameterGroup operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • DbParameterGroupAlreadyExistsException A DB parameter group with the same name exists.
      • DbParameterGroupQuotaExceededException Request would result in user exceeding the allowed number of DB parameter groups.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • copyDBParameterGroup

      default CompletableFuture<CopyDbParameterGroupResponse> copyDBParameterGroup(Consumer<CopyDbParameterGroupRequest.Builder> copyDbParameterGroupRequest)

      Copies the specified DB parameter group.


      This is a convenience which creates an instance of the CopyDbParameterGroupRequest.Builder avoiding the need to create one manually via CopyDbParameterGroupRequest.builder()

      Parameters:
      copyDbParameterGroupRequest - A Consumer that will call methods on CopyDbParameterGroupRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the CopyDBParameterGroup operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • DbParameterGroupAlreadyExistsException A DB parameter group with the same name exists.
      • DbParameterGroupQuotaExceededException Request would result in user exceeding the allowed number of DB parameter groups.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createDBCluster

      default CompletableFuture<CreateDbClusterResponse> createDBCluster(CreateDbClusterRequest createDbClusterRequest)

      Creates a new Amazon Neptune DB cluster.

      You can use the ReplicationSourceIdentifier parameter to create the DB cluster as a Read Replica of another DB cluster or Amazon Neptune DB instance.

      Note that when you create a new cluster using CreateDBCluster directly, deletion protection is disabled by default (when you create a new production cluster in the console, deletion protection is enabled by default). You can only delete a DB cluster if its DeletionProtection field is set to false.

      Parameters:
      createDbClusterRequest -
      Returns:
      A Java Future containing the result of the CreateDBCluster operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterAlreadyExistsException User already has a DB cluster with the given identifier.
      • InsufficientStorageClusterCapacityException There is insufficient storage available for the current action. You may be able to resolve this error by updating your subnet group to use different Availability Zones that have more storage available.
      • DbClusterQuotaExceededException User attempted to create a new DB cluster and the user has already reached the maximum allowed DB cluster quota.
      • StorageQuotaExceededException Request would result in user exceeding the allowed amount of storage available across all DB instances.
      • DbSubnetGroupNotFoundException DBSubnetGroupName does not refer to an existing DB subnet group.
      • InvalidVpcNetworkStateException DB subnet group does not cover all Availability Zones after it is created because users' change.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • InvalidDbSubnetGroupStateException The DB subnet group cannot be deleted because it is in use.
      • InvalidSubnetException The requested subnet is invalid, or multiple subnets were requested that are not all in a common VPC.
      • InvalidDbInstanceStateException The specified DB instance is not in the available state.
      • DbClusterParameterGroupNotFoundException DBClusterParameterGroupName does not refer to an existing DB Cluster parameter group.
      • KmsKeyNotAccessibleException Error accessing KMS key.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • DbInstanceNotFoundException DBInstanceIdentifier does not refer to an existing DB instance.
      • DbSubnetGroupDoesNotCoverEnoughAZsException Subnets in the DB subnet group should cover at least two Availability Zones unless there is only one Availability Zone.
      • GlobalClusterNotFoundException The GlobalClusterIdentifier doesn't refer to an existing global database cluster.
      • InvalidGlobalClusterStateException The global cluster is in an invalid state and can't perform the requested operation.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createDBCluster

      default CompletableFuture<CreateDbClusterResponse> createDBCluster(Consumer<CreateDbClusterRequest.Builder> createDbClusterRequest)

      Creates a new Amazon Neptune DB cluster.

      You can use the ReplicationSourceIdentifier parameter to create the DB cluster as a Read Replica of another DB cluster or Amazon Neptune DB instance.

      Note that when you create a new cluster using CreateDBCluster directly, deletion protection is disabled by default (when you create a new production cluster in the console, deletion protection is enabled by default). You can only delete a DB cluster if its DeletionProtection field is set to false.


      This is a convenience which creates an instance of the CreateDbClusterRequest.Builder avoiding the need to create one manually via CreateDbClusterRequest.builder()

      Parameters:
      createDbClusterRequest - A Consumer that will call methods on CreateDbClusterRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the CreateDBCluster operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterAlreadyExistsException User already has a DB cluster with the given identifier.
      • InsufficientStorageClusterCapacityException There is insufficient storage available for the current action. You may be able to resolve this error by updating your subnet group to use different Availability Zones that have more storage available.
      • DbClusterQuotaExceededException User attempted to create a new DB cluster and the user has already reached the maximum allowed DB cluster quota.
      • StorageQuotaExceededException Request would result in user exceeding the allowed amount of storage available across all DB instances.
      • DbSubnetGroupNotFoundException DBSubnetGroupName does not refer to an existing DB subnet group.
      • InvalidVpcNetworkStateException DB subnet group does not cover all Availability Zones after it is created because users' change.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • InvalidDbSubnetGroupStateException The DB subnet group cannot be deleted because it is in use.
      • InvalidSubnetException The requested subnet is invalid, or multiple subnets were requested that are not all in a common VPC.
      • InvalidDbInstanceStateException The specified DB instance is not in the available state.
      • DbClusterParameterGroupNotFoundException DBClusterParameterGroupName does not refer to an existing DB Cluster parameter group.
      • KmsKeyNotAccessibleException Error accessing KMS key.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • DbInstanceNotFoundException DBInstanceIdentifier does not refer to an existing DB instance.
      • DbSubnetGroupDoesNotCoverEnoughAZsException Subnets in the DB subnet group should cover at least two Availability Zones unless there is only one Availability Zone.
      • GlobalClusterNotFoundException The GlobalClusterIdentifier doesn't refer to an existing global database cluster.
      • InvalidGlobalClusterStateException The global cluster is in an invalid state and can't perform the requested operation.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createDBClusterEndpoint

      default CompletableFuture<CreateDbClusterEndpointResponse> createDBClusterEndpoint(CreateDbClusterEndpointRequest createDbClusterEndpointRequest)

      Creates a new custom endpoint and associates it with an Amazon Neptune DB cluster.

      Parameters:
      createDbClusterEndpointRequest -
      Returns:
      A Java Future containing the result of the CreateDBClusterEndpoint operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterEndpointQuotaExceededException The cluster already has the maximum number of custom endpoints.
      • DbClusterEndpointAlreadyExistsException The specified custom endpoint cannot be created because it already exists.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • DbInstanceNotFoundException DBInstanceIdentifier does not refer to an existing DB instance.
      • InvalidDbInstanceStateException The specified DB instance is not in the available state.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createDBClusterEndpoint

      default CompletableFuture<CreateDbClusterEndpointResponse> createDBClusterEndpoint(Consumer<CreateDbClusterEndpointRequest.Builder> createDbClusterEndpointRequest)

      Creates a new custom endpoint and associates it with an Amazon Neptune DB cluster.


      This is a convenience which creates an instance of the CreateDbClusterEndpointRequest.Builder avoiding the need to create one manually via CreateDbClusterEndpointRequest.builder()

      Parameters:
      createDbClusterEndpointRequest - A Consumer that will call methods on CreateDbClusterEndpointRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the CreateDBClusterEndpoint operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterEndpointQuotaExceededException The cluster already has the maximum number of custom endpoints.
      • DbClusterEndpointAlreadyExistsException The specified custom endpoint cannot be created because it already exists.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • DbInstanceNotFoundException DBInstanceIdentifier does not refer to an existing DB instance.
      • InvalidDbInstanceStateException The specified DB instance is not in the available state.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createDBClusterParameterGroup

      default CompletableFuture<CreateDbClusterParameterGroupResponse> createDBClusterParameterGroup(CreateDbClusterParameterGroupRequest createDbClusterParameterGroupRequest)

      Creates a new DB cluster parameter group.

      Parameters in a DB cluster parameter group apply to all of the instances in a DB cluster.

      A DB cluster parameter group is initially created with the default parameters for the database engine used by instances in the DB cluster. To provide custom values for any of the parameters, you must modify the group after creating it using ModifyDBClusterParameterGroup. Once you've created a DB cluster parameter group, you need to associate it with your DB cluster using ModifyDBCluster. When you associate a new DB cluster parameter group with a running DB cluster, you need to reboot the DB instances in the DB cluster without failover for the new DB cluster parameter group and associated settings to take effect.

      After you create a DB cluster parameter group, you should wait at least 5 minutes before creating your first DB cluster that uses that DB cluster parameter group as the default parameter group. This allows Amazon Neptune to fully complete the create action before the DB cluster parameter group is used as the default for a new DB cluster. This is especially important for parameters that are critical when creating the default database for a DB cluster, such as the character set for the default database defined by the character_set_database parameter. You can use the Parameter Groups option of the Amazon Neptune console or the DescribeDBClusterParameters command to verify that your DB cluster parameter group has been created or modified.

      Parameters:
      createDbClusterParameterGroupRequest -
      Returns:
      A Java Future containing the result of the CreateDBClusterParameterGroup operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupQuotaExceededException Request would result in user exceeding the allowed number of DB parameter groups.
      • DbParameterGroupAlreadyExistsException A DB parameter group with the same name exists.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createDBClusterParameterGroup

      default CompletableFuture<CreateDbClusterParameterGroupResponse> createDBClusterParameterGroup(Consumer<CreateDbClusterParameterGroupRequest.Builder> createDbClusterParameterGroupRequest)

      Creates a new DB cluster parameter group.

      Parameters in a DB cluster parameter group apply to all of the instances in a DB cluster.

      A DB cluster parameter group is initially created with the default parameters for the database engine used by instances in the DB cluster. To provide custom values for any of the parameters, you must modify the group after creating it using ModifyDBClusterParameterGroup. Once you've created a DB cluster parameter group, you need to associate it with your DB cluster using ModifyDBCluster. When you associate a new DB cluster parameter group with a running DB cluster, you need to reboot the DB instances in the DB cluster without failover for the new DB cluster parameter group and associated settings to take effect.

      After you create a DB cluster parameter group, you should wait at least 5 minutes before creating your first DB cluster that uses that DB cluster parameter group as the default parameter group. This allows Amazon Neptune to fully complete the create action before the DB cluster parameter group is used as the default for a new DB cluster. This is especially important for parameters that are critical when creating the default database for a DB cluster, such as the character set for the default database defined by the character_set_database parameter. You can use the Parameter Groups option of the Amazon Neptune console or the DescribeDBClusterParameters command to verify that your DB cluster parameter group has been created or modified.


      This is a convenience which creates an instance of the CreateDbClusterParameterGroupRequest.Builder avoiding the need to create one manually via CreateDbClusterParameterGroupRequest.builder()

      Parameters:
      createDbClusterParameterGroupRequest - A Consumer that will call methods on CreateDbClusterParameterGroupRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the CreateDBClusterParameterGroup operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupQuotaExceededException Request would result in user exceeding the allowed number of DB parameter groups.
      • DbParameterGroupAlreadyExistsException A DB parameter group with the same name exists.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createDBClusterSnapshot

      default CompletableFuture<CreateDbClusterSnapshotResponse> createDBClusterSnapshot(CreateDbClusterSnapshotRequest createDbClusterSnapshotRequest)

      Creates a snapshot of a DB cluster.

      Parameters:
      createDbClusterSnapshotRequest -
      Returns:
      A Java Future containing the result of the CreateDBClusterSnapshot operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterSnapshotAlreadyExistsException User already has a DB cluster snapshot with the given identifier.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • SnapshotQuotaExceededException Request would result in user exceeding the allowed number of DB snapshots.
      • InvalidDbClusterSnapshotStateException The supplied value is not a valid DB cluster snapshot state.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createDBClusterSnapshot

      default CompletableFuture<CreateDbClusterSnapshotResponse> createDBClusterSnapshot(Consumer<CreateDbClusterSnapshotRequest.Builder> createDbClusterSnapshotRequest)

      Creates a snapshot of a DB cluster.


      This is a convenience which creates an instance of the CreateDbClusterSnapshotRequest.Builder avoiding the need to create one manually via CreateDbClusterSnapshotRequest.builder()

      Parameters:
      createDbClusterSnapshotRequest - A Consumer that will call methods on CreateDbClusterSnapshotRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the CreateDBClusterSnapshot operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterSnapshotAlreadyExistsException User already has a DB cluster snapshot with the given identifier.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • SnapshotQuotaExceededException Request would result in user exceeding the allowed number of DB snapshots.
      • InvalidDbClusterSnapshotStateException The supplied value is not a valid DB cluster snapshot state.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createDBInstance

      default CompletableFuture<CreateDbInstanceResponse> createDBInstance(CreateDbInstanceRequest createDbInstanceRequest)

      Creates a new DB instance.

      Parameters:
      createDbInstanceRequest -
      Returns:
      A Java Future containing the result of the CreateDBInstance operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbInstanceAlreadyExistsException User already has a DB instance with the given identifier.
      • InsufficientDbInstanceCapacityException Specified DB instance class is not available in the specified Availability Zone.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • DbSecurityGroupNotFoundException DBSecurityGroupName does not refer to an existing DB security group.
      • InstanceQuotaExceededException Request would result in user exceeding the allowed number of DB instances.
      • StorageQuotaExceededException Request would result in user exceeding the allowed amount of storage available across all DB instances.
      • DbSubnetGroupNotFoundException DBSubnetGroupName does not refer to an existing DB subnet group.
      • DbSubnetGroupDoesNotCoverEnoughAZsException Subnets in the DB subnet group should cover at least two Availability Zones unless there is only one Availability Zone.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • InvalidSubnetException The requested subnet is invalid, or multiple subnets were requested that are not all in a common VPC.
      • InvalidVpcNetworkStateException DB subnet group does not cover all Availability Zones after it is created because users' change.
      • ProvisionedIopsNotAvailableInAzException Provisioned IOPS not available in the specified Availability Zone.
      • OptionGroupNotFoundException The designated option group could not be found.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • StorageTypeNotSupportedException StorageType specified cannot be associated with the DB Instance.
      • AuthorizationNotFoundException Specified CIDRIP or EC2 security group is not authorized for the specified DB security group.

        Neptune may not also be authorized via IAM to perform necessary actions on your behalf.

      • KmsKeyNotAccessibleException Error accessing KMS key.
      • DomainNotFoundException Domain does not refer to an existing Active Directory Domain.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createDBInstance

      default CompletableFuture<CreateDbInstanceResponse> createDBInstance(Consumer<CreateDbInstanceRequest.Builder> createDbInstanceRequest)

      Creates a new DB instance.


      This is a convenience which creates an instance of the CreateDbInstanceRequest.Builder avoiding the need to create one manually via CreateDbInstanceRequest.builder()

      Parameters:
      createDbInstanceRequest - A Consumer that will call methods on CreateDbInstanceRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the CreateDBInstance operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbInstanceAlreadyExistsException User already has a DB instance with the given identifier.
      • InsufficientDbInstanceCapacityException Specified DB instance class is not available in the specified Availability Zone.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • DbSecurityGroupNotFoundException DBSecurityGroupName does not refer to an existing DB security group.
      • InstanceQuotaExceededException Request would result in user exceeding the allowed number of DB instances.
      • StorageQuotaExceededException Request would result in user exceeding the allowed amount of storage available across all DB instances.
      • DbSubnetGroupNotFoundException DBSubnetGroupName does not refer to an existing DB subnet group.
      • DbSubnetGroupDoesNotCoverEnoughAZsException Subnets in the DB subnet group should cover at least two Availability Zones unless there is only one Availability Zone.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • InvalidSubnetException The requested subnet is invalid, or multiple subnets were requested that are not all in a common VPC.
      • InvalidVpcNetworkStateException DB subnet group does not cover all Availability Zones after it is created because users' change.
      • ProvisionedIopsNotAvailableInAzException Provisioned IOPS not available in the specified Availability Zone.
      • OptionGroupNotFoundException The designated option group could not be found.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • StorageTypeNotSupportedException StorageType specified cannot be associated with the DB Instance.
      • AuthorizationNotFoundException Specified CIDRIP or EC2 security group is not authorized for the specified DB security group.

        Neptune may not also be authorized via IAM to perform necessary actions on your behalf.

      • KmsKeyNotAccessibleException Error accessing KMS key.
      • DomainNotFoundException Domain does not refer to an existing Active Directory Domain.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createDBParameterGroup

      default CompletableFuture<CreateDbParameterGroupResponse> createDBParameterGroup(CreateDbParameterGroupRequest createDbParameterGroupRequest)

      Creates a new DB parameter group.

      A DB parameter group is initially created with the default parameters for the database engine used by the DB instance. To provide custom values for any of the parameters, you must modify the group after creating it using ModifyDBParameterGroup. Once you've created a DB parameter group, you need to associate it with your DB instance using ModifyDBInstance. When you associate a new DB parameter group with a running DB instance, you need to reboot the DB instance without failover for the new DB parameter group and associated settings to take effect.

      After you create a DB parameter group, you should wait at least 5 minutes before creating your first DB instance that uses that DB parameter group as the default parameter group. This allows Amazon Neptune to fully complete the create action before the parameter group is used as the default for a new DB instance. This is especially important for parameters that are critical when creating the default database for a DB instance, such as the character set for the default database defined by the character_set_database parameter. You can use the Parameter Groups option of the Amazon Neptune console or the DescribeDBParameters command to verify that your DB parameter group has been created or modified.

      Parameters:
      createDbParameterGroupRequest -
      Returns:
      A Java Future containing the result of the CreateDBParameterGroup operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupQuotaExceededException Request would result in user exceeding the allowed number of DB parameter groups.
      • DbParameterGroupAlreadyExistsException A DB parameter group with the same name exists.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createDBParameterGroup

      default CompletableFuture<CreateDbParameterGroupResponse> createDBParameterGroup(Consumer<CreateDbParameterGroupRequest.Builder> createDbParameterGroupRequest)

      Creates a new DB parameter group.

      A DB parameter group is initially created with the default parameters for the database engine used by the DB instance. To provide custom values for any of the parameters, you must modify the group after creating it using ModifyDBParameterGroup. Once you've created a DB parameter group, you need to associate it with your DB instance using ModifyDBInstance. When you associate a new DB parameter group with a running DB instance, you need to reboot the DB instance without failover for the new DB parameter group and associated settings to take effect.

      After you create a DB parameter group, you should wait at least 5 minutes before creating your first DB instance that uses that DB parameter group as the default parameter group. This allows Amazon Neptune to fully complete the create action before the parameter group is used as the default for a new DB instance. This is especially important for parameters that are critical when creating the default database for a DB instance, such as the character set for the default database defined by the character_set_database parameter. You can use the Parameter Groups option of the Amazon Neptune console or the DescribeDBParameters command to verify that your DB parameter group has been created or modified.


      This is a convenience which creates an instance of the CreateDbParameterGroupRequest.Builder avoiding the need to create one manually via CreateDbParameterGroupRequest.builder()

      Parameters:
      createDbParameterGroupRequest - A Consumer that will call methods on CreateDbParameterGroupRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the CreateDBParameterGroup operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupQuotaExceededException Request would result in user exceeding the allowed number of DB parameter groups.
      • DbParameterGroupAlreadyExistsException A DB parameter group with the same name exists.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createDBSubnetGroup

      default CompletableFuture<CreateDbSubnetGroupResponse> createDBSubnetGroup(CreateDbSubnetGroupRequest createDbSubnetGroupRequest)

      Creates a new DB subnet group. DB subnet groups must contain at least one subnet in at least two AZs in the Amazon Region.

      Parameters:
      createDbSubnetGroupRequest -
      Returns:
      A Java Future containing the result of the CreateDBSubnetGroup operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbSubnetGroupAlreadyExistsException DBSubnetGroupName is already used by an existing DB subnet group.
      • DbSubnetGroupQuotaExceededException Request would result in user exceeding the allowed number of DB subnet groups.
      • DbSubnetQuotaExceededException Request would result in user exceeding the allowed number of subnets in a DB subnet groups.
      • DbSubnetGroupDoesNotCoverEnoughAZsException Subnets in the DB subnet group should cover at least two Availability Zones unless there is only one Availability Zone.
      • InvalidSubnetException The requested subnet is invalid, or multiple subnets were requested that are not all in a common VPC.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createDBSubnetGroup

      default CompletableFuture<CreateDbSubnetGroupResponse> createDBSubnetGroup(Consumer<CreateDbSubnetGroupRequest.Builder> createDbSubnetGroupRequest)

      Creates a new DB subnet group. DB subnet groups must contain at least one subnet in at least two AZs in the Amazon Region.


      This is a convenience which creates an instance of the CreateDbSubnetGroupRequest.Builder avoiding the need to create one manually via CreateDbSubnetGroupRequest.builder()

      Parameters:
      createDbSubnetGroupRequest - A Consumer that will call methods on CreateDbSubnetGroupRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the CreateDBSubnetGroup operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbSubnetGroupAlreadyExistsException DBSubnetGroupName is already used by an existing DB subnet group.
      • DbSubnetGroupQuotaExceededException Request would result in user exceeding the allowed number of DB subnet groups.
      • DbSubnetQuotaExceededException Request would result in user exceeding the allowed number of subnets in a DB subnet groups.
      • DbSubnetGroupDoesNotCoverEnoughAZsException Subnets in the DB subnet group should cover at least two Availability Zones unless there is only one Availability Zone.
      • InvalidSubnetException The requested subnet is invalid, or multiple subnets were requested that are not all in a common VPC.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createEventSubscription

      default CompletableFuture<CreateEventSubscriptionResponse> createEventSubscription(CreateEventSubscriptionRequest createEventSubscriptionRequest)

      Creates an event notification subscription. This action requires a topic ARN (Amazon Resource Name) created by either the Neptune console, the SNS console, or the SNS API. To obtain an ARN with SNS, you must create a topic in Amazon SNS and subscribe to the topic. The ARN is displayed in the SNS console.

      You can specify the type of source (SourceType) you want to be notified of, provide a list of Neptune sources (SourceIds) that triggers the events, and provide a list of event categories (EventCategories) for events you want to be notified of. For example, you can specify SourceType = db-instance, SourceIds = mydbinstance1, mydbinstance2 and EventCategories = Availability, Backup.

      If you specify both the SourceType and SourceIds, such as SourceType = db-instance and SourceIdentifier = myDBInstance1, you are notified of all the db-instance events for the specified source. If you specify a SourceType but do not specify a SourceIdentifier, you receive notice of the events for that source type for all your Neptune sources. If you do not specify either the SourceType nor the SourceIdentifier, you are notified of events generated from all Neptune sources belonging to your customer account.

      Parameters:
      createEventSubscriptionRequest -
      Returns:
      A Java Future containing the result of the CreateEventSubscription operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • EventSubscriptionQuotaExceededException You have exceeded the number of events you can subscribe to.
      • SubscriptionAlreadyExistException This subscription already exists.
      • SnsInvalidTopicException The SNS topic is invalid.
      • SnsNoAuthorizationException There is no SNS authorization.
      • SnsTopicArnNotFoundException The ARN of the SNS topic could not be found.
      • SubscriptionCategoryNotFoundException The designated subscription category could not be found.
      • SourceNotFoundException The source could not be found.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createEventSubscription

      default CompletableFuture<CreateEventSubscriptionResponse> createEventSubscription(Consumer<CreateEventSubscriptionRequest.Builder> createEventSubscriptionRequest)

      Creates an event notification subscription. This action requires a topic ARN (Amazon Resource Name) created by either the Neptune console, the SNS console, or the SNS API. To obtain an ARN with SNS, you must create a topic in Amazon SNS and subscribe to the topic. The ARN is displayed in the SNS console.

      You can specify the type of source (SourceType) you want to be notified of, provide a list of Neptune sources (SourceIds) that triggers the events, and provide a list of event categories (EventCategories) for events you want to be notified of. For example, you can specify SourceType = db-instance, SourceIds = mydbinstance1, mydbinstance2 and EventCategories = Availability, Backup.

      If you specify both the SourceType and SourceIds, such as SourceType = db-instance and SourceIdentifier = myDBInstance1, you are notified of all the db-instance events for the specified source. If you specify a SourceType but do not specify a SourceIdentifier, you receive notice of the events for that source type for all your Neptune sources. If you do not specify either the SourceType nor the SourceIdentifier, you are notified of events generated from all Neptune sources belonging to your customer account.


      This is a convenience which creates an instance of the CreateEventSubscriptionRequest.Builder avoiding the need to create one manually via CreateEventSubscriptionRequest.builder()

      Parameters:
      createEventSubscriptionRequest - A Consumer that will call methods on CreateEventSubscriptionRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the CreateEventSubscription operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • EventSubscriptionQuotaExceededException You have exceeded the number of events you can subscribe to.
      • SubscriptionAlreadyExistException This subscription already exists.
      • SnsInvalidTopicException The SNS topic is invalid.
      • SnsNoAuthorizationException There is no SNS authorization.
      • SnsTopicArnNotFoundException The ARN of the SNS topic could not be found.
      • SubscriptionCategoryNotFoundException The designated subscription category could not be found.
      • SourceNotFoundException The source could not be found.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createGlobalCluster

      default CompletableFuture<CreateGlobalClusterResponse> createGlobalCluster(CreateGlobalClusterRequest createGlobalClusterRequest)

      Creates a Neptune global database spread across multiple Amazon Regions. The global database contains a single primary cluster with read-write capability, and read-only secondary clusters that receive data from the primary cluster through high-speed replication performed by the Neptune storage subsystem.

      You can create a global database that is initially empty, and then add a primary cluster and secondary clusters to it, or you can specify an existing Neptune cluster during the create operation to become the primary cluster of the global database.

      Parameters:
      createGlobalClusterRequest -
      Returns:
      A Java Future containing the result of the CreateGlobalCluster operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • GlobalClusterAlreadyExistsException The GlobalClusterIdentifier already exists. Choose a new global database identifier (unique name) to create a new global database cluster.
      • GlobalClusterQuotaExceededException The number of global database clusters for this account is already at the maximum allowed.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • createGlobalCluster

      default CompletableFuture<CreateGlobalClusterResponse> createGlobalCluster(Consumer<CreateGlobalClusterRequest.Builder> createGlobalClusterRequest)

      Creates a Neptune global database spread across multiple Amazon Regions. The global database contains a single primary cluster with read-write capability, and read-only secondary clusters that receive data from the primary cluster through high-speed replication performed by the Neptune storage subsystem.

      You can create a global database that is initially empty, and then add a primary cluster and secondary clusters to it, or you can specify an existing Neptune cluster during the create operation to become the primary cluster of the global database.


      This is a convenience which creates an instance of the CreateGlobalClusterRequest.Builder avoiding the need to create one manually via CreateGlobalClusterRequest.builder()

      Parameters:
      createGlobalClusterRequest - A Consumer that will call methods on CreateGlobalClusterRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the CreateGlobalCluster operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • GlobalClusterAlreadyExistsException The GlobalClusterIdentifier already exists. Choose a new global database identifier (unique name) to create a new global database cluster.
      • GlobalClusterQuotaExceededException The number of global database clusters for this account is already at the maximum allowed.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteDBCluster

      default CompletableFuture<DeleteDbClusterResponse> deleteDBCluster(DeleteDbClusterRequest deleteDbClusterRequest)

      The DeleteDBCluster action deletes a previously provisioned DB cluster. When you delete a DB cluster, all automated backups for that DB cluster are deleted and can't be recovered. Manual DB cluster snapshots of the specified DB cluster are not deleted.

      Note that the DB Cluster cannot be deleted if deletion protection is enabled. To delete it, you must first set its DeletionProtection field to False.

      Parameters:
      deleteDbClusterRequest -
      Returns:
      A Java Future containing the result of the DeleteDBCluster operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • DbClusterSnapshotAlreadyExistsException User already has a DB cluster snapshot with the given identifier.
      • SnapshotQuotaExceededException Request would result in user exceeding the allowed number of DB snapshots.
      • InvalidDbClusterSnapshotStateException The supplied value is not a valid DB cluster snapshot state.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteDBCluster

      default CompletableFuture<DeleteDbClusterResponse> deleteDBCluster(Consumer<DeleteDbClusterRequest.Builder> deleteDbClusterRequest)

      The DeleteDBCluster action deletes a previously provisioned DB cluster. When you delete a DB cluster, all automated backups for that DB cluster are deleted and can't be recovered. Manual DB cluster snapshots of the specified DB cluster are not deleted.

      Note that the DB Cluster cannot be deleted if deletion protection is enabled. To delete it, you must first set its DeletionProtection field to False.


      This is a convenience which creates an instance of the DeleteDbClusterRequest.Builder avoiding the need to create one manually via DeleteDbClusterRequest.builder()

      Parameters:
      deleteDbClusterRequest - A Consumer that will call methods on DeleteDbClusterRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DeleteDBCluster operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • DbClusterSnapshotAlreadyExistsException User already has a DB cluster snapshot with the given identifier.
      • SnapshotQuotaExceededException Request would result in user exceeding the allowed number of DB snapshots.
      • InvalidDbClusterSnapshotStateException The supplied value is not a valid DB cluster snapshot state.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteDBClusterEndpoint

      default CompletableFuture<DeleteDbClusterEndpointResponse> deleteDBClusterEndpoint(DeleteDbClusterEndpointRequest deleteDbClusterEndpointRequest)

      Deletes a custom endpoint and removes it from an Amazon Neptune DB cluster.

      Parameters:
      deleteDbClusterEndpointRequest -
      Returns:
      A Java Future containing the result of the DeleteDBClusterEndpoint operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidDbClusterEndpointStateException The requested operation cannot be performed on the endpoint while the endpoint is in this state.
      • DbClusterEndpointNotFoundException The specified custom endpoint doesn't exist.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteDBClusterEndpoint

      default CompletableFuture<DeleteDbClusterEndpointResponse> deleteDBClusterEndpoint(Consumer<DeleteDbClusterEndpointRequest.Builder> deleteDbClusterEndpointRequest)

      Deletes a custom endpoint and removes it from an Amazon Neptune DB cluster.


      This is a convenience which creates an instance of the DeleteDbClusterEndpointRequest.Builder avoiding the need to create one manually via DeleteDbClusterEndpointRequest.builder()

      Parameters:
      deleteDbClusterEndpointRequest - A Consumer that will call methods on DeleteDbClusterEndpointRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DeleteDBClusterEndpoint operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidDbClusterEndpointStateException The requested operation cannot be performed on the endpoint while the endpoint is in this state.
      • DbClusterEndpointNotFoundException The specified custom endpoint doesn't exist.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteDBClusterParameterGroup

      default CompletableFuture<DeleteDbClusterParameterGroupResponse> deleteDBClusterParameterGroup(DeleteDbClusterParameterGroupRequest deleteDbClusterParameterGroupRequest)

      Deletes a specified DB cluster parameter group. The DB cluster parameter group to be deleted can't be associated with any DB clusters.

      Parameters:
      deleteDbClusterParameterGroupRequest -
      Returns:
      A Java Future containing the result of the DeleteDBClusterParameterGroup operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidDbParameterGroupStateException The DB parameter group is in use or is in an invalid state. If you are attempting to delete the parameter group, you cannot delete it when the parameter group is in this state.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteDBClusterParameterGroup

      default CompletableFuture<DeleteDbClusterParameterGroupResponse> deleteDBClusterParameterGroup(Consumer<DeleteDbClusterParameterGroupRequest.Builder> deleteDbClusterParameterGroupRequest)

      Deletes a specified DB cluster parameter group. The DB cluster parameter group to be deleted can't be associated with any DB clusters.


      This is a convenience which creates an instance of the DeleteDbClusterParameterGroupRequest.Builder avoiding the need to create one manually via DeleteDbClusterParameterGroupRequest.builder()

      Parameters:
      deleteDbClusterParameterGroupRequest - A Consumer that will call methods on DeleteDbClusterParameterGroupRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DeleteDBClusterParameterGroup operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidDbParameterGroupStateException The DB parameter group is in use or is in an invalid state. If you are attempting to delete the parameter group, you cannot delete it when the parameter group is in this state.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteDBClusterSnapshot

      default CompletableFuture<DeleteDbClusterSnapshotResponse> deleteDBClusterSnapshot(DeleteDbClusterSnapshotRequest deleteDbClusterSnapshotRequest)

      Deletes a DB cluster snapshot. If the snapshot is being copied, the copy operation is terminated.

      The DB cluster snapshot must be in the available state to be deleted.

      Parameters:
      deleteDbClusterSnapshotRequest -
      Returns:
      A Java Future containing the result of the DeleteDBClusterSnapshot operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidDbClusterSnapshotStateException The supplied value is not a valid DB cluster snapshot state.
      • DbClusterSnapshotNotFoundException DBClusterSnapshotIdentifier does not refer to an existing DB cluster snapshot.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteDBClusterSnapshot

      default CompletableFuture<DeleteDbClusterSnapshotResponse> deleteDBClusterSnapshot(Consumer<DeleteDbClusterSnapshotRequest.Builder> deleteDbClusterSnapshotRequest)

      Deletes a DB cluster snapshot. If the snapshot is being copied, the copy operation is terminated.

      The DB cluster snapshot must be in the available state to be deleted.


      This is a convenience which creates an instance of the DeleteDbClusterSnapshotRequest.Builder avoiding the need to create one manually via DeleteDbClusterSnapshotRequest.builder()

      Parameters:
      deleteDbClusterSnapshotRequest - A Consumer that will call methods on DeleteDbClusterSnapshotRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DeleteDBClusterSnapshot operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidDbClusterSnapshotStateException The supplied value is not a valid DB cluster snapshot state.
      • DbClusterSnapshotNotFoundException DBClusterSnapshotIdentifier does not refer to an existing DB cluster snapshot.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteDBInstance

      default CompletableFuture<DeleteDbInstanceResponse> deleteDBInstance(DeleteDbInstanceRequest deleteDbInstanceRequest)

      The DeleteDBInstance action deletes a previously provisioned DB instance. When you delete a DB instance, all automated backups for that instance are deleted and can't be recovered. Manual DB snapshots of the DB instance to be deleted by DeleteDBInstance are not deleted.

      If you request a final DB snapshot the status of the Amazon Neptune DB instance is deleting until the DB snapshot is created. The API action DescribeDBInstance is used to monitor the status of this operation. The action can't be canceled or reverted once submitted.

      Note that when a DB instance is in a failure state and has a status of failed, incompatible-restore, or incompatible-network, you can only delete it when the SkipFinalSnapshot parameter is set to true.

      You can't delete a DB instance if it is the only instance in the DB cluster, or if it has deletion protection enabled.

      Parameters:
      deleteDbInstanceRequest -
      Returns:
      A Java Future containing the result of the DeleteDBInstance operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbInstanceNotFoundException DBInstanceIdentifier does not refer to an existing DB instance.
      • InvalidDbInstanceStateException The specified DB instance is not in the available state.
      • DbSnapshotAlreadyExistsException DBSnapshotIdentifier is already used by an existing snapshot.
      • SnapshotQuotaExceededException Request would result in user exceeding the allowed number of DB snapshots.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteDBInstance

      default CompletableFuture<DeleteDbInstanceResponse> deleteDBInstance(Consumer<DeleteDbInstanceRequest.Builder> deleteDbInstanceRequest)

      The DeleteDBInstance action deletes a previously provisioned DB instance. When you delete a DB instance, all automated backups for that instance are deleted and can't be recovered. Manual DB snapshots of the DB instance to be deleted by DeleteDBInstance are not deleted.

      If you request a final DB snapshot the status of the Amazon Neptune DB instance is deleting until the DB snapshot is created. The API action DescribeDBInstance is used to monitor the status of this operation. The action can't be canceled or reverted once submitted.

      Note that when a DB instance is in a failure state and has a status of failed, incompatible-restore, or incompatible-network, you can only delete it when the SkipFinalSnapshot parameter is set to true.

      You can't delete a DB instance if it is the only instance in the DB cluster, or if it has deletion protection enabled.


      This is a convenience which creates an instance of the DeleteDbInstanceRequest.Builder avoiding the need to create one manually via DeleteDbInstanceRequest.builder()

      Parameters:
      deleteDbInstanceRequest - A Consumer that will call methods on DeleteDbInstanceRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DeleteDBInstance operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbInstanceNotFoundException DBInstanceIdentifier does not refer to an existing DB instance.
      • InvalidDbInstanceStateException The specified DB instance is not in the available state.
      • DbSnapshotAlreadyExistsException DBSnapshotIdentifier is already used by an existing snapshot.
      • SnapshotQuotaExceededException Request would result in user exceeding the allowed number of DB snapshots.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteDBParameterGroup

      default CompletableFuture<DeleteDbParameterGroupResponse> deleteDBParameterGroup(DeleteDbParameterGroupRequest deleteDbParameterGroupRequest)

      Deletes a specified DBParameterGroup. The DBParameterGroup to be deleted can't be associated with any DB instances.

      Parameters:
      deleteDbParameterGroupRequest -
      Returns:
      A Java Future containing the result of the DeleteDBParameterGroup operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidDbParameterGroupStateException The DB parameter group is in use or is in an invalid state. If you are attempting to delete the parameter group, you cannot delete it when the parameter group is in this state.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteDBParameterGroup

      default CompletableFuture<DeleteDbParameterGroupResponse> deleteDBParameterGroup(Consumer<DeleteDbParameterGroupRequest.Builder> deleteDbParameterGroupRequest)

      Deletes a specified DBParameterGroup. The DBParameterGroup to be deleted can't be associated with any DB instances.


      This is a convenience which creates an instance of the DeleteDbParameterGroupRequest.Builder avoiding the need to create one manually via DeleteDbParameterGroupRequest.builder()

      Parameters:
      deleteDbParameterGroupRequest - A Consumer that will call methods on DeleteDbParameterGroupRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DeleteDBParameterGroup operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidDbParameterGroupStateException The DB parameter group is in use or is in an invalid state. If you are attempting to delete the parameter group, you cannot delete it when the parameter group is in this state.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteDBSubnetGroup

      default CompletableFuture<DeleteDbSubnetGroupResponse> deleteDBSubnetGroup(DeleteDbSubnetGroupRequest deleteDbSubnetGroupRequest)

      Deletes a DB subnet group.

      The specified database subnet group must not be associated with any DB instances.

      Parameters:
      deleteDbSubnetGroupRequest -
      Returns:
      A Java Future containing the result of the DeleteDBSubnetGroup operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidDbSubnetGroupStateException The DB subnet group cannot be deleted because it is in use.
      • InvalidDbSubnetStateException The DB subnet is not in the available state.
      • DbSubnetGroupNotFoundException DBSubnetGroupName does not refer to an existing DB subnet group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteDBSubnetGroup

      default CompletableFuture<DeleteDbSubnetGroupResponse> deleteDBSubnetGroup(Consumer<DeleteDbSubnetGroupRequest.Builder> deleteDbSubnetGroupRequest)

      Deletes a DB subnet group.

      The specified database subnet group must not be associated with any DB instances.


      This is a convenience which creates an instance of the DeleteDbSubnetGroupRequest.Builder avoiding the need to create one manually via DeleteDbSubnetGroupRequest.builder()

      Parameters:
      deleteDbSubnetGroupRequest - A Consumer that will call methods on DeleteDbSubnetGroupRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DeleteDBSubnetGroup operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidDbSubnetGroupStateException The DB subnet group cannot be deleted because it is in use.
      • InvalidDbSubnetStateException The DB subnet is not in the available state.
      • DbSubnetGroupNotFoundException DBSubnetGroupName does not refer to an existing DB subnet group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteEventSubscription

      default CompletableFuture<DeleteEventSubscriptionResponse> deleteEventSubscription(DeleteEventSubscriptionRequest deleteEventSubscriptionRequest)

      Deletes an event notification subscription.

      Parameters:
      deleteEventSubscriptionRequest -
      Returns:
      A Java Future containing the result of the DeleteEventSubscription operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SubscriptionNotFoundException The designated subscription could not be found.
      • InvalidEventSubscriptionStateException The event subscription is in an invalid state.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteEventSubscription

      default CompletableFuture<DeleteEventSubscriptionResponse> deleteEventSubscription(Consumer<DeleteEventSubscriptionRequest.Builder> deleteEventSubscriptionRequest)

      Deletes an event notification subscription.


      This is a convenience which creates an instance of the DeleteEventSubscriptionRequest.Builder avoiding the need to create one manually via DeleteEventSubscriptionRequest.builder()

      Parameters:
      deleteEventSubscriptionRequest - A Consumer that will call methods on DeleteEventSubscriptionRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DeleteEventSubscription operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SubscriptionNotFoundException The designated subscription could not be found.
      • InvalidEventSubscriptionStateException The event subscription is in an invalid state.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteGlobalCluster

      default CompletableFuture<DeleteGlobalClusterResponse> deleteGlobalCluster(DeleteGlobalClusterRequest deleteGlobalClusterRequest)

      Deletes a global database. The primary and all secondary clusters must already be detached or deleted first.

      Parameters:
      deleteGlobalClusterRequest -
      Returns:
      A Java Future containing the result of the DeleteGlobalCluster operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • GlobalClusterNotFoundException The GlobalClusterIdentifier doesn't refer to an existing global database cluster.
      • InvalidGlobalClusterStateException The global cluster is in an invalid state and can't perform the requested operation.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • deleteGlobalCluster

      default CompletableFuture<DeleteGlobalClusterResponse> deleteGlobalCluster(Consumer<DeleteGlobalClusterRequest.Builder> deleteGlobalClusterRequest)

      Deletes a global database. The primary and all secondary clusters must already be detached or deleted first.


      This is a convenience which creates an instance of the DeleteGlobalClusterRequest.Builder avoiding the need to create one manually via DeleteGlobalClusterRequest.builder()

      Parameters:
      deleteGlobalClusterRequest - A Consumer that will call methods on DeleteGlobalClusterRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DeleteGlobalCluster operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • GlobalClusterNotFoundException The GlobalClusterIdentifier doesn't refer to an existing global database cluster.
      • InvalidGlobalClusterStateException The global cluster is in an invalid state and can't perform the requested operation.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBClusterEndpoints

      default CompletableFuture<DescribeDbClusterEndpointsResponse> describeDBClusterEndpoints(DescribeDbClusterEndpointsRequest describeDbClusterEndpointsRequest)

      Returns information about endpoints for an Amazon Neptune DB cluster.

      This operation can also return information for Amazon RDS clusters and Amazon DocDB clusters.

      Parameters:
      describeDbClusterEndpointsRequest -
      Returns:
      A Java Future containing the result of the DescribeDBClusterEndpoints operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBClusterEndpoints

      default CompletableFuture<DescribeDbClusterEndpointsResponse> describeDBClusterEndpoints(Consumer<DescribeDbClusterEndpointsRequest.Builder> describeDbClusterEndpointsRequest)

      Returns information about endpoints for an Amazon Neptune DB cluster.

      This operation can also return information for Amazon RDS clusters and Amazon DocDB clusters.


      This is a convenience which creates an instance of the DescribeDbClusterEndpointsRequest.Builder avoiding the need to create one manually via DescribeDbClusterEndpointsRequest.builder()

      Parameters:
      describeDbClusterEndpointsRequest - A Consumer that will call methods on DescribeDbClusterEndpointsRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DescribeDBClusterEndpoints operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBClusterEndpointsPaginator

      default DescribeDBClusterEndpointsPublisher describeDBClusterEndpointsPaginator(DescribeDbClusterEndpointsRequest describeDbClusterEndpointsRequest)

      This is a variant of describeDBClusterEndpoints(software.amazon.awssdk.services.neptune.model.DescribeDbClusterEndpointsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeDBClusterEndpointsPublisher publisher = client.describeDBClusterEndpointsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeDBClusterEndpointsPublisher publisher = client.describeDBClusterEndpointsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeDbClusterEndpointsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeDbClusterEndpointsResponse 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 MaxRecords 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 describeDBClusterEndpoints(software.amazon.awssdk.services.neptune.model.DescribeDbClusterEndpointsRequest) operation.

      Parameters:
      describeDbClusterEndpointsRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBClusterEndpointsPaginator

      default DescribeDBClusterEndpointsPublisher describeDBClusterEndpointsPaginator(Consumer<DescribeDbClusterEndpointsRequest.Builder> describeDbClusterEndpointsRequest)

      This is a variant of describeDBClusterEndpoints(software.amazon.awssdk.services.neptune.model.DescribeDbClusterEndpointsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeDBClusterEndpointsPublisher publisher = client.describeDBClusterEndpointsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeDBClusterEndpointsPublisher publisher = client.describeDBClusterEndpointsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeDbClusterEndpointsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeDbClusterEndpointsResponse 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 MaxRecords 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 describeDBClusterEndpoints(software.amazon.awssdk.services.neptune.model.DescribeDbClusterEndpointsRequest) operation.


      This is a convenience which creates an instance of the DescribeDbClusterEndpointsRequest.Builder avoiding the need to create one manually via DescribeDbClusterEndpointsRequest.builder()

      Parameters:
      describeDbClusterEndpointsRequest - A Consumer that will call methods on DescribeDbClusterEndpointsRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBClusterParameterGroups

      default CompletableFuture<DescribeDbClusterParameterGroupsResponse> describeDBClusterParameterGroups(DescribeDbClusterParameterGroupsRequest describeDbClusterParameterGroupsRequest)

      Returns a list of DBClusterParameterGroup descriptions. If a DBClusterParameterGroupName parameter is specified, the list will contain only the description of the specified DB cluster parameter group.

      Parameters:
      describeDbClusterParameterGroupsRequest -
      Returns:
      A Java Future containing the result of the DescribeDBClusterParameterGroups operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBClusterParameterGroups

      default CompletableFuture<DescribeDbClusterParameterGroupsResponse> describeDBClusterParameterGroups(Consumer<DescribeDbClusterParameterGroupsRequest.Builder> describeDbClusterParameterGroupsRequest)

      Returns a list of DBClusterParameterGroup descriptions. If a DBClusterParameterGroupName parameter is specified, the list will contain only the description of the specified DB cluster parameter group.


      This is a convenience which creates an instance of the DescribeDbClusterParameterGroupsRequest.Builder avoiding the need to create one manually via DescribeDbClusterParameterGroupsRequest.builder()

      Parameters:
      describeDbClusterParameterGroupsRequest - A Consumer that will call methods on DescribeDbClusterParameterGroupsRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DescribeDBClusterParameterGroups operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBClusterParameterGroups

      default CompletableFuture<DescribeDbClusterParameterGroupsResponse> describeDBClusterParameterGroups()

      Returns a list of DBClusterParameterGroup descriptions. If a DBClusterParameterGroupName parameter is specified, the list will contain only the description of the specified DB cluster parameter group.

      Returns:
      A Java Future containing the result of the DescribeDBClusterParameterGroups operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBClusterParameterGroupsPaginator

      default DescribeDBClusterParameterGroupsPublisher describeDBClusterParameterGroupsPaginator()

      This is a variant of describeDBClusterParameterGroups(software.amazon.awssdk.services.neptune.model.DescribeDbClusterParameterGroupsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeDBClusterParameterGroupsPublisher publisher = client.describeDBClusterParameterGroupsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeDBClusterParameterGroupsPublisher publisher = client.describeDBClusterParameterGroupsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeDbClusterParameterGroupsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeDbClusterParameterGroupsResponse 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 MaxRecords 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 describeDBClusterParameterGroups(software.amazon.awssdk.services.neptune.model.DescribeDbClusterParameterGroupsRequest) operation.

      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBClusterParameterGroupsPaginator

      default DescribeDBClusterParameterGroupsPublisher describeDBClusterParameterGroupsPaginator(DescribeDbClusterParameterGroupsRequest describeDbClusterParameterGroupsRequest)

      This is a variant of describeDBClusterParameterGroups(software.amazon.awssdk.services.neptune.model.DescribeDbClusterParameterGroupsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeDBClusterParameterGroupsPublisher publisher = client.describeDBClusterParameterGroupsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeDBClusterParameterGroupsPublisher publisher = client.describeDBClusterParameterGroupsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeDbClusterParameterGroupsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeDbClusterParameterGroupsResponse 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 MaxRecords 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 describeDBClusterParameterGroups(software.amazon.awssdk.services.neptune.model.DescribeDbClusterParameterGroupsRequest) operation.

      Parameters:
      describeDbClusterParameterGroupsRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBClusterParameterGroupsPaginator

      default DescribeDBClusterParameterGroupsPublisher describeDBClusterParameterGroupsPaginator(Consumer<DescribeDbClusterParameterGroupsRequest.Builder> describeDbClusterParameterGroupsRequest)

      This is a variant of describeDBClusterParameterGroups(software.amazon.awssdk.services.neptune.model.DescribeDbClusterParameterGroupsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeDBClusterParameterGroupsPublisher publisher = client.describeDBClusterParameterGroupsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeDBClusterParameterGroupsPublisher publisher = client.describeDBClusterParameterGroupsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeDbClusterParameterGroupsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeDbClusterParameterGroupsResponse 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 MaxRecords 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 describeDBClusterParameterGroups(software.amazon.awssdk.services.neptune.model.DescribeDbClusterParameterGroupsRequest) operation.


      This is a convenience which creates an instance of the DescribeDbClusterParameterGroupsRequest.Builder avoiding the need to create one manually via DescribeDbClusterParameterGroupsRequest.builder()

      Parameters:
      describeDbClusterParameterGroupsRequest - A Consumer that will call methods on DescribeDbClusterParameterGroupsRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBClusterParameters

      default CompletableFuture<DescribeDbClusterParametersResponse> describeDBClusterParameters(DescribeDbClusterParametersRequest describeDbClusterParametersRequest)

      Returns the detailed parameter list for a particular DB cluster parameter group.

      Parameters:
      describeDbClusterParametersRequest -
      Returns:
      A Java Future containing the result of the DescribeDBClusterParameters operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBClusterParameters

      default CompletableFuture<DescribeDbClusterParametersResponse> describeDBClusterParameters(Consumer<DescribeDbClusterParametersRequest.Builder> describeDbClusterParametersRequest)

      Returns the detailed parameter list for a particular DB cluster parameter group.


      This is a convenience which creates an instance of the DescribeDbClusterParametersRequest.Builder avoiding the need to create one manually via DescribeDbClusterParametersRequest.builder()

      Parameters:
      describeDbClusterParametersRequest - A Consumer that will call methods on DescribeDbClusterParametersRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DescribeDBClusterParameters operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBClusterParametersPaginator

      default DescribeDBClusterParametersPublisher describeDBClusterParametersPaginator(DescribeDbClusterParametersRequest describeDbClusterParametersRequest)

      This is a variant of describeDBClusterParameters(software.amazon.awssdk.services.neptune.model.DescribeDbClusterParametersRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeDBClusterParametersPublisher publisher = client.describeDBClusterParametersPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeDBClusterParametersPublisher publisher = client.describeDBClusterParametersPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeDbClusterParametersResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeDbClusterParametersResponse 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 MaxRecords 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 describeDBClusterParameters(software.amazon.awssdk.services.neptune.model.DescribeDbClusterParametersRequest) operation.

      Parameters:
      describeDbClusterParametersRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBClusterParametersPaginator

      default DescribeDBClusterParametersPublisher describeDBClusterParametersPaginator(Consumer<DescribeDbClusterParametersRequest.Builder> describeDbClusterParametersRequest)

      This is a variant of describeDBClusterParameters(software.amazon.awssdk.services.neptune.model.DescribeDbClusterParametersRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeDBClusterParametersPublisher publisher = client.describeDBClusterParametersPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeDBClusterParametersPublisher publisher = client.describeDBClusterParametersPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeDbClusterParametersResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeDbClusterParametersResponse 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 MaxRecords 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 describeDBClusterParameters(software.amazon.awssdk.services.neptune.model.DescribeDbClusterParametersRequest) operation.


      This is a convenience which creates an instance of the DescribeDbClusterParametersRequest.Builder avoiding the need to create one manually via DescribeDbClusterParametersRequest.builder()

      Parameters:
      describeDbClusterParametersRequest - A Consumer that will call methods on DescribeDbClusterParametersRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBClusterSnapshotAttributes

      default CompletableFuture<DescribeDbClusterSnapshotAttributesResponse> describeDBClusterSnapshotAttributes(DescribeDbClusterSnapshotAttributesRequest describeDbClusterSnapshotAttributesRequest)

      Returns a list of DB cluster snapshot attribute names and values for a manual DB cluster snapshot.

      When sharing snapshots with other Amazon accounts, DescribeDBClusterSnapshotAttributes returns the restore attribute and a list of IDs for the Amazon accounts that are authorized to copy or restore the manual DB cluster snapshot. If all is included in the list of values for the restore attribute, then the manual DB cluster snapshot is public and can be copied or restored by all Amazon accounts.

      To add or remove access for an Amazon account to copy or restore a manual DB cluster snapshot, or to make the manual DB cluster snapshot public or private, use the ModifyDBClusterSnapshotAttribute API action.

      Parameters:
      describeDbClusterSnapshotAttributesRequest -
      Returns:
      A Java Future containing the result of the DescribeDBClusterSnapshotAttributes operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterSnapshotNotFoundException DBClusterSnapshotIdentifier does not refer to an existing DB cluster snapshot.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBClusterSnapshotAttributes

      default CompletableFuture<DescribeDbClusterSnapshotAttributesResponse> describeDBClusterSnapshotAttributes(Consumer<DescribeDbClusterSnapshotAttributesRequest.Builder> describeDbClusterSnapshotAttributesRequest)

      Returns a list of DB cluster snapshot attribute names and values for a manual DB cluster snapshot.

      When sharing snapshots with other Amazon accounts, DescribeDBClusterSnapshotAttributes returns the restore attribute and a list of IDs for the Amazon accounts that are authorized to copy or restore the manual DB cluster snapshot. If all is included in the list of values for the restore attribute, then the manual DB cluster snapshot is public and can be copied or restored by all Amazon accounts.

      To add or remove access for an Amazon account to copy or restore a manual DB cluster snapshot, or to make the manual DB cluster snapshot public or private, use the ModifyDBClusterSnapshotAttribute API action.


      This is a convenience which creates an instance of the DescribeDbClusterSnapshotAttributesRequest.Builder avoiding the need to create one manually via DescribeDbClusterSnapshotAttributesRequest.builder()

      Parameters:
      describeDbClusterSnapshotAttributesRequest - A Consumer that will call methods on DescribeDbClusterSnapshotAttributesRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DescribeDBClusterSnapshotAttributes operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterSnapshotNotFoundException DBClusterSnapshotIdentifier does not refer to an existing DB cluster snapshot.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBClusterSnapshots

      default CompletableFuture<DescribeDbClusterSnapshotsResponse> describeDBClusterSnapshots(DescribeDbClusterSnapshotsRequest describeDbClusterSnapshotsRequest)

      Returns information about DB cluster snapshots. This API action supports pagination.

      Parameters:
      describeDbClusterSnapshotsRequest -
      Returns:
      A Java Future containing the result of the DescribeDBClusterSnapshots operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterSnapshotNotFoundException DBClusterSnapshotIdentifier does not refer to an existing DB cluster snapshot.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBClusterSnapshots

      default CompletableFuture<DescribeDbClusterSnapshotsResponse> describeDBClusterSnapshots(Consumer<DescribeDbClusterSnapshotsRequest.Builder> describeDbClusterSnapshotsRequest)

      Returns information about DB cluster snapshots. This API action supports pagination.


      This is a convenience which creates an instance of the DescribeDbClusterSnapshotsRequest.Builder avoiding the need to create one manually via DescribeDbClusterSnapshotsRequest.builder()

      Parameters:
      describeDbClusterSnapshotsRequest - A Consumer that will call methods on DescribeDbClusterSnapshotsRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DescribeDBClusterSnapshots operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterSnapshotNotFoundException DBClusterSnapshotIdentifier does not refer to an existing DB cluster snapshot.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBClusterSnapshots

      default CompletableFuture<DescribeDbClusterSnapshotsResponse> describeDBClusterSnapshots()

      Returns information about DB cluster snapshots. This API action supports pagination.

      Returns:
      A Java Future containing the result of the DescribeDBClusterSnapshots operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterSnapshotNotFoundException DBClusterSnapshotIdentifier does not refer to an existing DB cluster snapshot.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBClusterSnapshotsPaginator

      default DescribeDBClusterSnapshotsPublisher describeDBClusterSnapshotsPaginator()

      This is a variant of describeDBClusterSnapshots(software.amazon.awssdk.services.neptune.model.DescribeDbClusterSnapshotsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeDBClusterSnapshotsPublisher publisher = client.describeDBClusterSnapshotsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeDBClusterSnapshotsPublisher publisher = client.describeDBClusterSnapshotsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeDbClusterSnapshotsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeDbClusterSnapshotsResponse 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 MaxRecords 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 describeDBClusterSnapshots(software.amazon.awssdk.services.neptune.model.DescribeDbClusterSnapshotsRequest) operation.

      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterSnapshotNotFoundException DBClusterSnapshotIdentifier does not refer to an existing DB cluster snapshot.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBClusterSnapshotsPaginator

      default DescribeDBClusterSnapshotsPublisher describeDBClusterSnapshotsPaginator(DescribeDbClusterSnapshotsRequest describeDbClusterSnapshotsRequest)

      This is a variant of describeDBClusterSnapshots(software.amazon.awssdk.services.neptune.model.DescribeDbClusterSnapshotsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeDBClusterSnapshotsPublisher publisher = client.describeDBClusterSnapshotsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeDBClusterSnapshotsPublisher publisher = client.describeDBClusterSnapshotsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeDbClusterSnapshotsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeDbClusterSnapshotsResponse 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 MaxRecords 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 describeDBClusterSnapshots(software.amazon.awssdk.services.neptune.model.DescribeDbClusterSnapshotsRequest) operation.

      Parameters:
      describeDbClusterSnapshotsRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterSnapshotNotFoundException DBClusterSnapshotIdentifier does not refer to an existing DB cluster snapshot.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBClusterSnapshotsPaginator

      default DescribeDBClusterSnapshotsPublisher describeDBClusterSnapshotsPaginator(Consumer<DescribeDbClusterSnapshotsRequest.Builder> describeDbClusterSnapshotsRequest)

      This is a variant of describeDBClusterSnapshots(software.amazon.awssdk.services.neptune.model.DescribeDbClusterSnapshotsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeDBClusterSnapshotsPublisher publisher = client.describeDBClusterSnapshotsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeDBClusterSnapshotsPublisher publisher = client.describeDBClusterSnapshotsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeDbClusterSnapshotsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeDbClusterSnapshotsResponse 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 MaxRecords 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 describeDBClusterSnapshots(software.amazon.awssdk.services.neptune.model.DescribeDbClusterSnapshotsRequest) operation.


      This is a convenience which creates an instance of the DescribeDbClusterSnapshotsRequest.Builder avoiding the need to create one manually via DescribeDbClusterSnapshotsRequest.builder()

      Parameters:
      describeDbClusterSnapshotsRequest - A Consumer that will call methods on DescribeDbClusterSnapshotsRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterSnapshotNotFoundException DBClusterSnapshotIdentifier does not refer to an existing DB cluster snapshot.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBClusters

      default CompletableFuture<DescribeDbClustersResponse> describeDBClusters(DescribeDbClustersRequest describeDbClustersRequest)

      Returns information about provisioned DB clusters, and supports pagination.

      This operation can also return information for Amazon RDS clusters and Amazon DocDB clusters.

      Parameters:
      describeDbClustersRequest -
      Returns:
      A Java Future containing the result of the DescribeDBClusters operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBClusters

      default CompletableFuture<DescribeDbClustersResponse> describeDBClusters(Consumer<DescribeDbClustersRequest.Builder> describeDbClustersRequest)

      Returns information about provisioned DB clusters, and supports pagination.

      This operation can also return information for Amazon RDS clusters and Amazon DocDB clusters.


      This is a convenience which creates an instance of the DescribeDbClustersRequest.Builder avoiding the need to create one manually via DescribeDbClustersRequest.builder()

      Parameters:
      describeDbClustersRequest - A Consumer that will call methods on DescribeDbClustersRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DescribeDBClusters operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBClusters

      default CompletableFuture<DescribeDbClustersResponse> describeDBClusters()

      Returns information about provisioned DB clusters, and supports pagination.

      This operation can also return information for Amazon RDS clusters and Amazon DocDB clusters.

      Returns:
      A Java Future containing the result of the DescribeDBClusters operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBClustersPaginator

      default DescribeDBClustersPublisher describeDBClustersPaginator()

      This is a variant of describeDBClusters(software.amazon.awssdk.services.neptune.model.DescribeDbClustersRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeDBClustersPublisher publisher = client.describeDBClustersPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeDBClustersPublisher publisher = client.describeDBClustersPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeDbClustersResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeDbClustersResponse 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 MaxRecords 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 describeDBClusters(software.amazon.awssdk.services.neptune.model.DescribeDbClustersRequest) operation.

      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBClustersPaginator

      default DescribeDBClustersPublisher describeDBClustersPaginator(DescribeDbClustersRequest describeDbClustersRequest)

      This is a variant of describeDBClusters(software.amazon.awssdk.services.neptune.model.DescribeDbClustersRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeDBClustersPublisher publisher = client.describeDBClustersPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeDBClustersPublisher publisher = client.describeDBClustersPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeDbClustersResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeDbClustersResponse 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 MaxRecords 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 describeDBClusters(software.amazon.awssdk.services.neptune.model.DescribeDbClustersRequest) operation.

      Parameters:
      describeDbClustersRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBClustersPaginator

      default DescribeDBClustersPublisher describeDBClustersPaginator(Consumer<DescribeDbClustersRequest.Builder> describeDbClustersRequest)

      This is a variant of describeDBClusters(software.amazon.awssdk.services.neptune.model.DescribeDbClustersRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeDBClustersPublisher publisher = client.describeDBClustersPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeDBClustersPublisher publisher = client.describeDBClustersPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeDbClustersResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeDbClustersResponse 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 MaxRecords 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 describeDBClusters(software.amazon.awssdk.services.neptune.model.DescribeDbClustersRequest) operation.


      This is a convenience which creates an instance of the DescribeDbClustersRequest.Builder avoiding the need to create one manually via DescribeDbClustersRequest.builder()

      Parameters:
      describeDbClustersRequest - A Consumer that will call methods on DescribeDbClustersRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBEngineVersions

      default CompletableFuture<DescribeDbEngineVersionsResponse> describeDBEngineVersions(DescribeDbEngineVersionsRequest describeDbEngineVersionsRequest)

      Returns a list of the available DB engines.

      Parameters:
      describeDbEngineVersionsRequest -
      Returns:
      A Java Future containing the result of the DescribeDBEngineVersions operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBEngineVersions

      default CompletableFuture<DescribeDbEngineVersionsResponse> describeDBEngineVersions(Consumer<DescribeDbEngineVersionsRequest.Builder> describeDbEngineVersionsRequest)

      Returns a list of the available DB engines.


      This is a convenience which creates an instance of the DescribeDbEngineVersionsRequest.Builder avoiding the need to create one manually via DescribeDbEngineVersionsRequest.builder()

      Parameters:
      describeDbEngineVersionsRequest - A Consumer that will call methods on DescribeDbEngineVersionsRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DescribeDBEngineVersions operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBEngineVersions

      default CompletableFuture<DescribeDbEngineVersionsResponse> describeDBEngineVersions()

      Returns a list of the available DB engines.

      Returns:
      A Java Future containing the result of the DescribeDBEngineVersions operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBEngineVersionsPaginator

      default DescribeDBEngineVersionsPublisher describeDBEngineVersionsPaginator()

      This is a variant of describeDBEngineVersions(software.amazon.awssdk.services.neptune.model.DescribeDbEngineVersionsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeDBEngineVersionsPublisher publisher = client.describeDBEngineVersionsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeDBEngineVersionsPublisher publisher = client.describeDBEngineVersionsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeDbEngineVersionsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeDbEngineVersionsResponse 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 MaxRecords 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 describeDBEngineVersions(software.amazon.awssdk.services.neptune.model.DescribeDbEngineVersionsRequest) operation.

      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBEngineVersionsPaginator

      default DescribeDBEngineVersionsPublisher describeDBEngineVersionsPaginator(DescribeDbEngineVersionsRequest describeDbEngineVersionsRequest)

      This is a variant of describeDBEngineVersions(software.amazon.awssdk.services.neptune.model.DescribeDbEngineVersionsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeDBEngineVersionsPublisher publisher = client.describeDBEngineVersionsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeDBEngineVersionsPublisher publisher = client.describeDBEngineVersionsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeDbEngineVersionsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeDbEngineVersionsResponse 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 MaxRecords 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 describeDBEngineVersions(software.amazon.awssdk.services.neptune.model.DescribeDbEngineVersionsRequest) operation.

      Parameters:
      describeDbEngineVersionsRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBEngineVersionsPaginator

      default DescribeDBEngineVersionsPublisher describeDBEngineVersionsPaginator(Consumer<DescribeDbEngineVersionsRequest.Builder> describeDbEngineVersionsRequest)

      This is a variant of describeDBEngineVersions(software.amazon.awssdk.services.neptune.model.DescribeDbEngineVersionsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeDBEngineVersionsPublisher publisher = client.describeDBEngineVersionsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeDBEngineVersionsPublisher publisher = client.describeDBEngineVersionsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeDbEngineVersionsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeDbEngineVersionsResponse 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 MaxRecords 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 describeDBEngineVersions(software.amazon.awssdk.services.neptune.model.DescribeDbEngineVersionsRequest) operation.


      This is a convenience which creates an instance of the DescribeDbEngineVersionsRequest.Builder avoiding the need to create one manually via DescribeDbEngineVersionsRequest.builder()

      Parameters:
      describeDbEngineVersionsRequest - A Consumer that will call methods on DescribeDbEngineVersionsRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBInstances

      default CompletableFuture<DescribeDbInstancesResponse> describeDBInstances(DescribeDbInstancesRequest describeDbInstancesRequest)

      Returns information about provisioned instances, and supports pagination.

      This operation can also return information for Amazon RDS instances and Amazon DocDB instances.

      Parameters:
      describeDbInstancesRequest -
      Returns:
      A Java Future containing the result of the DescribeDBInstances operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbInstanceNotFoundException DBInstanceIdentifier does not refer to an existing DB instance.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBInstances

      default CompletableFuture<DescribeDbInstancesResponse> describeDBInstances(Consumer<DescribeDbInstancesRequest.Builder> describeDbInstancesRequest)

      Returns information about provisioned instances, and supports pagination.

      This operation can also return information for Amazon RDS instances and Amazon DocDB instances.


      This is a convenience which creates an instance of the DescribeDbInstancesRequest.Builder avoiding the need to create one manually via DescribeDbInstancesRequest.builder()

      Parameters:
      describeDbInstancesRequest - A Consumer that will call methods on DescribeDbInstancesRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DescribeDBInstances operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbInstanceNotFoundException DBInstanceIdentifier does not refer to an existing DB instance.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBInstances

      default CompletableFuture<DescribeDbInstancesResponse> describeDBInstances()

      Returns information about provisioned instances, and supports pagination.

      This operation can also return information for Amazon RDS instances and Amazon DocDB instances.

      Returns:
      A Java Future containing the result of the DescribeDBInstances operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbInstanceNotFoundException DBInstanceIdentifier does not refer to an existing DB instance.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBInstancesPaginator

      default DescribeDBInstancesPublisher describeDBInstancesPaginator()

      This is a variant of describeDBInstances(software.amazon.awssdk.services.neptune.model.DescribeDbInstancesRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeDBInstancesPublisher publisher = client.describeDBInstancesPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeDBInstancesPublisher publisher = client.describeDBInstancesPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeDbInstancesResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeDbInstancesResponse 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 MaxRecords 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 describeDBInstances(software.amazon.awssdk.services.neptune.model.DescribeDbInstancesRequest) operation.

      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbInstanceNotFoundException DBInstanceIdentifier does not refer to an existing DB instance.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBInstancesPaginator

      default DescribeDBInstancesPublisher describeDBInstancesPaginator(DescribeDbInstancesRequest describeDbInstancesRequest)

      This is a variant of describeDBInstances(software.amazon.awssdk.services.neptune.model.DescribeDbInstancesRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeDBInstancesPublisher publisher = client.describeDBInstancesPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeDBInstancesPublisher publisher = client.describeDBInstancesPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeDbInstancesResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeDbInstancesResponse 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 MaxRecords 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 describeDBInstances(software.amazon.awssdk.services.neptune.model.DescribeDbInstancesRequest) operation.

      Parameters:
      describeDbInstancesRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbInstanceNotFoundException DBInstanceIdentifier does not refer to an existing DB instance.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBInstancesPaginator

      default DescribeDBInstancesPublisher describeDBInstancesPaginator(Consumer<DescribeDbInstancesRequest.Builder> describeDbInstancesRequest)

      This is a variant of describeDBInstances(software.amazon.awssdk.services.neptune.model.DescribeDbInstancesRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeDBInstancesPublisher publisher = client.describeDBInstancesPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeDBInstancesPublisher publisher = client.describeDBInstancesPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeDbInstancesResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeDbInstancesResponse 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 MaxRecords 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 describeDBInstances(software.amazon.awssdk.services.neptune.model.DescribeDbInstancesRequest) operation.


      This is a convenience which creates an instance of the DescribeDbInstancesRequest.Builder avoiding the need to create one manually via DescribeDbInstancesRequest.builder()

      Parameters:
      describeDbInstancesRequest - A Consumer that will call methods on DescribeDbInstancesRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbInstanceNotFoundException DBInstanceIdentifier does not refer to an existing DB instance.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBParameterGroups

      default CompletableFuture<DescribeDbParameterGroupsResponse> describeDBParameterGroups(DescribeDbParameterGroupsRequest describeDbParameterGroupsRequest)

      Returns a list of DBParameterGroup descriptions. If a DBParameterGroupName is specified, the list will contain only the description of the specified DB parameter group.

      Parameters:
      describeDbParameterGroupsRequest -
      Returns:
      A Java Future containing the result of the DescribeDBParameterGroups operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBParameterGroups

      default CompletableFuture<DescribeDbParameterGroupsResponse> describeDBParameterGroups(Consumer<DescribeDbParameterGroupsRequest.Builder> describeDbParameterGroupsRequest)

      Returns a list of DBParameterGroup descriptions. If a DBParameterGroupName is specified, the list will contain only the description of the specified DB parameter group.


      This is a convenience which creates an instance of the DescribeDbParameterGroupsRequest.Builder avoiding the need to create one manually via DescribeDbParameterGroupsRequest.builder()

      Parameters:
      describeDbParameterGroupsRequest - A Consumer that will call methods on DescribeDbParameterGroupsRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DescribeDBParameterGroups operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBParameterGroups

      default CompletableFuture<DescribeDbParameterGroupsResponse> describeDBParameterGroups()

      Returns a list of DBParameterGroup descriptions. If a DBParameterGroupName is specified, the list will contain only the description of the specified DB parameter group.

      Returns:
      A Java Future containing the result of the DescribeDBParameterGroups operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBParameterGroupsPaginator

      default DescribeDBParameterGroupsPublisher describeDBParameterGroupsPaginator()

      This is a variant of describeDBParameterGroups(software.amazon.awssdk.services.neptune.model.DescribeDbParameterGroupsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeDBParameterGroupsPublisher publisher = client.describeDBParameterGroupsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeDBParameterGroupsPublisher publisher = client.describeDBParameterGroupsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeDbParameterGroupsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeDbParameterGroupsResponse 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 MaxRecords 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 describeDBParameterGroups(software.amazon.awssdk.services.neptune.model.DescribeDbParameterGroupsRequest) operation.

      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBParameterGroupsPaginator

      default DescribeDBParameterGroupsPublisher describeDBParameterGroupsPaginator(DescribeDbParameterGroupsRequest describeDbParameterGroupsRequest)

      This is a variant of describeDBParameterGroups(software.amazon.awssdk.services.neptune.model.DescribeDbParameterGroupsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeDBParameterGroupsPublisher publisher = client.describeDBParameterGroupsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeDBParameterGroupsPublisher publisher = client.describeDBParameterGroupsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeDbParameterGroupsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeDbParameterGroupsResponse 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 MaxRecords 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 describeDBParameterGroups(software.amazon.awssdk.services.neptune.model.DescribeDbParameterGroupsRequest) operation.

      Parameters:
      describeDbParameterGroupsRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBParameterGroupsPaginator

      default DescribeDBParameterGroupsPublisher describeDBParameterGroupsPaginator(Consumer<DescribeDbParameterGroupsRequest.Builder> describeDbParameterGroupsRequest)

      This is a variant of describeDBParameterGroups(software.amazon.awssdk.services.neptune.model.DescribeDbParameterGroupsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeDBParameterGroupsPublisher publisher = client.describeDBParameterGroupsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeDBParameterGroupsPublisher publisher = client.describeDBParameterGroupsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeDbParameterGroupsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeDbParameterGroupsResponse 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 MaxRecords 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 describeDBParameterGroups(software.amazon.awssdk.services.neptune.model.DescribeDbParameterGroupsRequest) operation.


      This is a convenience which creates an instance of the DescribeDbParameterGroupsRequest.Builder avoiding the need to create one manually via DescribeDbParameterGroupsRequest.builder()

      Parameters:
      describeDbParameterGroupsRequest - A Consumer that will call methods on DescribeDbParameterGroupsRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBParameters

      default CompletableFuture<DescribeDbParametersResponse> describeDBParameters(DescribeDbParametersRequest describeDbParametersRequest)

      Returns the detailed parameter list for a particular DB parameter group.

      Parameters:
      describeDbParametersRequest -
      Returns:
      A Java Future containing the result of the DescribeDBParameters operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBParameters

      default CompletableFuture<DescribeDbParametersResponse> describeDBParameters(Consumer<DescribeDbParametersRequest.Builder> describeDbParametersRequest)

      Returns the detailed parameter list for a particular DB parameter group.


      This is a convenience which creates an instance of the DescribeDbParametersRequest.Builder avoiding the need to create one manually via DescribeDbParametersRequest.builder()

      Parameters:
      describeDbParametersRequest - A Consumer that will call methods on DescribeDbParametersRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DescribeDBParameters operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBParametersPaginator

      default DescribeDBParametersPublisher describeDBParametersPaginator(DescribeDbParametersRequest describeDbParametersRequest)

      This is a variant of describeDBParameters(software.amazon.awssdk.services.neptune.model.DescribeDbParametersRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeDBParametersPublisher publisher = client.describeDBParametersPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeDBParametersPublisher publisher = client.describeDBParametersPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeDbParametersResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeDbParametersResponse 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 MaxRecords 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 describeDBParameters(software.amazon.awssdk.services.neptune.model.DescribeDbParametersRequest) operation.

      Parameters:
      describeDbParametersRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBParametersPaginator

      default DescribeDBParametersPublisher describeDBParametersPaginator(Consumer<DescribeDbParametersRequest.Builder> describeDbParametersRequest)

      This is a variant of describeDBParameters(software.amazon.awssdk.services.neptune.model.DescribeDbParametersRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeDBParametersPublisher publisher = client.describeDBParametersPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeDBParametersPublisher publisher = client.describeDBParametersPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeDbParametersResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeDbParametersResponse 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 MaxRecords 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 describeDBParameters(software.amazon.awssdk.services.neptune.model.DescribeDbParametersRequest) operation.


      This is a convenience which creates an instance of the DescribeDbParametersRequest.Builder avoiding the need to create one manually via DescribeDbParametersRequest.builder()

      Parameters:
      describeDbParametersRequest - A Consumer that will call methods on DescribeDbParametersRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBSubnetGroups

      default CompletableFuture<DescribeDbSubnetGroupsResponse> describeDBSubnetGroups(DescribeDbSubnetGroupsRequest describeDbSubnetGroupsRequest)

      Returns a list of DBSubnetGroup descriptions. If a DBSubnetGroupName is specified, the list will contain only the descriptions of the specified DBSubnetGroup.

      For an overview of CIDR ranges, go to the Wikipedia Tutorial.

      Parameters:
      describeDbSubnetGroupsRequest -
      Returns:
      A Java Future containing the result of the DescribeDBSubnetGroups operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbSubnetGroupNotFoundException DBSubnetGroupName does not refer to an existing DB subnet group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBSubnetGroups

      default CompletableFuture<DescribeDbSubnetGroupsResponse> describeDBSubnetGroups(Consumer<DescribeDbSubnetGroupsRequest.Builder> describeDbSubnetGroupsRequest)

      Returns a list of DBSubnetGroup descriptions. If a DBSubnetGroupName is specified, the list will contain only the descriptions of the specified DBSubnetGroup.

      For an overview of CIDR ranges, go to the Wikipedia Tutorial.


      This is a convenience which creates an instance of the DescribeDbSubnetGroupsRequest.Builder avoiding the need to create one manually via DescribeDbSubnetGroupsRequest.builder()

      Parameters:
      describeDbSubnetGroupsRequest - A Consumer that will call methods on DescribeDbSubnetGroupsRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DescribeDBSubnetGroups operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbSubnetGroupNotFoundException DBSubnetGroupName does not refer to an existing DB subnet group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBSubnetGroups

      default CompletableFuture<DescribeDbSubnetGroupsResponse> describeDBSubnetGroups()

      Returns a list of DBSubnetGroup descriptions. If a DBSubnetGroupName is specified, the list will contain only the descriptions of the specified DBSubnetGroup.

      For an overview of CIDR ranges, go to the Wikipedia Tutorial.

      Returns:
      A Java Future containing the result of the DescribeDBSubnetGroups operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbSubnetGroupNotFoundException DBSubnetGroupName does not refer to an existing DB subnet group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBSubnetGroupsPaginator

      default DescribeDBSubnetGroupsPublisher describeDBSubnetGroupsPaginator()

      This is a variant of describeDBSubnetGroups(software.amazon.awssdk.services.neptune.model.DescribeDbSubnetGroupsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeDBSubnetGroupsPublisher publisher = client.describeDBSubnetGroupsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeDBSubnetGroupsPublisher publisher = client.describeDBSubnetGroupsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeDbSubnetGroupsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeDbSubnetGroupsResponse 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 MaxRecords 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 describeDBSubnetGroups(software.amazon.awssdk.services.neptune.model.DescribeDbSubnetGroupsRequest) operation.

      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbSubnetGroupNotFoundException DBSubnetGroupName does not refer to an existing DB subnet group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBSubnetGroupsPaginator

      default DescribeDBSubnetGroupsPublisher describeDBSubnetGroupsPaginator(DescribeDbSubnetGroupsRequest describeDbSubnetGroupsRequest)

      This is a variant of describeDBSubnetGroups(software.amazon.awssdk.services.neptune.model.DescribeDbSubnetGroupsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeDBSubnetGroupsPublisher publisher = client.describeDBSubnetGroupsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeDBSubnetGroupsPublisher publisher = client.describeDBSubnetGroupsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeDbSubnetGroupsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeDbSubnetGroupsResponse 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 MaxRecords 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 describeDBSubnetGroups(software.amazon.awssdk.services.neptune.model.DescribeDbSubnetGroupsRequest) operation.

      Parameters:
      describeDbSubnetGroupsRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbSubnetGroupNotFoundException DBSubnetGroupName does not refer to an existing DB subnet group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeDBSubnetGroupsPaginator

      default DescribeDBSubnetGroupsPublisher describeDBSubnetGroupsPaginator(Consumer<DescribeDbSubnetGroupsRequest.Builder> describeDbSubnetGroupsRequest)

      This is a variant of describeDBSubnetGroups(software.amazon.awssdk.services.neptune.model.DescribeDbSubnetGroupsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeDBSubnetGroupsPublisher publisher = client.describeDBSubnetGroupsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeDBSubnetGroupsPublisher publisher = client.describeDBSubnetGroupsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeDbSubnetGroupsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeDbSubnetGroupsResponse 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 MaxRecords 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 describeDBSubnetGroups(software.amazon.awssdk.services.neptune.model.DescribeDbSubnetGroupsRequest) operation.


      This is a convenience which creates an instance of the DescribeDbSubnetGroupsRequest.Builder avoiding the need to create one manually via DescribeDbSubnetGroupsRequest.builder()

      Parameters:
      describeDbSubnetGroupsRequest - A Consumer that will call methods on DescribeDbSubnetGroupsRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbSubnetGroupNotFoundException DBSubnetGroupName does not refer to an existing DB subnet group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeEngineDefaultClusterParameters

      default CompletableFuture<DescribeEngineDefaultClusterParametersResponse> describeEngineDefaultClusterParameters(DescribeEngineDefaultClusterParametersRequest describeEngineDefaultClusterParametersRequest)

      Returns the default engine and system parameter information for the cluster database engine.

      Parameters:
      describeEngineDefaultClusterParametersRequest -
      Returns:
      A Java Future containing the result of the DescribeEngineDefaultClusterParameters operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeEngineDefaultClusterParameters

      default CompletableFuture<DescribeEngineDefaultClusterParametersResponse> describeEngineDefaultClusterParameters(Consumer<DescribeEngineDefaultClusterParametersRequest.Builder> describeEngineDefaultClusterParametersRequest)

      Returns the default engine and system parameter information for the cluster database engine.


      This is a convenience which creates an instance of the DescribeEngineDefaultClusterParametersRequest.Builder avoiding the need to create one manually via DescribeEngineDefaultClusterParametersRequest.builder()

      Parameters:
      describeEngineDefaultClusterParametersRequest - A Consumer that will call methods on DescribeEngineDefaultClusterParametersRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DescribeEngineDefaultClusterParameters operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeEngineDefaultParameters

      default CompletableFuture<DescribeEngineDefaultParametersResponse> describeEngineDefaultParameters(DescribeEngineDefaultParametersRequest describeEngineDefaultParametersRequest)

      Returns the default engine and system parameter information for the specified database engine.

      Parameters:
      describeEngineDefaultParametersRequest -
      Returns:
      A Java Future containing the result of the DescribeEngineDefaultParameters operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeEngineDefaultParameters

      default CompletableFuture<DescribeEngineDefaultParametersResponse> describeEngineDefaultParameters(Consumer<DescribeEngineDefaultParametersRequest.Builder> describeEngineDefaultParametersRequest)

      Returns the default engine and system parameter information for the specified database engine.


      This is a convenience which creates an instance of the DescribeEngineDefaultParametersRequest.Builder avoiding the need to create one manually via DescribeEngineDefaultParametersRequest.builder()

      Parameters:
      describeEngineDefaultParametersRequest - A Consumer that will call methods on DescribeEngineDefaultParametersRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DescribeEngineDefaultParameters operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeEngineDefaultParametersPaginator

      default DescribeEngineDefaultParametersPublisher describeEngineDefaultParametersPaginator(DescribeEngineDefaultParametersRequest describeEngineDefaultParametersRequest)

      This is a variant of describeEngineDefaultParameters(software.amazon.awssdk.services.neptune.model.DescribeEngineDefaultParametersRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeEngineDefaultParametersPublisher publisher = client.describeEngineDefaultParametersPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeEngineDefaultParametersPublisher publisher = client.describeEngineDefaultParametersPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeEngineDefaultParametersResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeEngineDefaultParametersResponse 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 MaxRecords 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 describeEngineDefaultParameters(software.amazon.awssdk.services.neptune.model.DescribeEngineDefaultParametersRequest) operation.

      Parameters:
      describeEngineDefaultParametersRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeEngineDefaultParametersPaginator

      default DescribeEngineDefaultParametersPublisher describeEngineDefaultParametersPaginator(Consumer<DescribeEngineDefaultParametersRequest.Builder> describeEngineDefaultParametersRequest)

      This is a variant of describeEngineDefaultParameters(software.amazon.awssdk.services.neptune.model.DescribeEngineDefaultParametersRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeEngineDefaultParametersPublisher publisher = client.describeEngineDefaultParametersPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeEngineDefaultParametersPublisher publisher = client.describeEngineDefaultParametersPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeEngineDefaultParametersResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeEngineDefaultParametersResponse 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 MaxRecords 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 describeEngineDefaultParameters(software.amazon.awssdk.services.neptune.model.DescribeEngineDefaultParametersRequest) operation.


      This is a convenience which creates an instance of the DescribeEngineDefaultParametersRequest.Builder avoiding the need to create one manually via DescribeEngineDefaultParametersRequest.builder()

      Parameters:
      describeEngineDefaultParametersRequest - A Consumer that will call methods on DescribeEngineDefaultParametersRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeEventCategories

      default CompletableFuture<DescribeEventCategoriesResponse> describeEventCategories(DescribeEventCategoriesRequest describeEventCategoriesRequest)

      Displays a list of categories for all event source types, or, if specified, for a specified source type.

      Parameters:
      describeEventCategoriesRequest -
      Returns:
      A Java Future containing the result of the DescribeEventCategories operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeEventCategories

      default CompletableFuture<DescribeEventCategoriesResponse> describeEventCategories(Consumer<DescribeEventCategoriesRequest.Builder> describeEventCategoriesRequest)

      Displays a list of categories for all event source types, or, if specified, for a specified source type.


      This is a convenience which creates an instance of the DescribeEventCategoriesRequest.Builder avoiding the need to create one manually via DescribeEventCategoriesRequest.builder()

      Parameters:
      describeEventCategoriesRequest - A Consumer that will call methods on DescribeEventCategoriesRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DescribeEventCategories operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeEventCategories

      default CompletableFuture<DescribeEventCategoriesResponse> describeEventCategories()

      Displays a list of categories for all event source types, or, if specified, for a specified source type.

      Returns:
      A Java Future containing the result of the DescribeEventCategories operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeEventSubscriptions

      default CompletableFuture<DescribeEventSubscriptionsResponse> describeEventSubscriptions(DescribeEventSubscriptionsRequest describeEventSubscriptionsRequest)

      Lists all the subscription descriptions for a customer account. The description for a subscription includes SubscriptionName, SNSTopicARN, CustomerID, SourceType, SourceID, CreationTime, and Status.

      If you specify a SubscriptionName, lists the description for that subscription.

      Parameters:
      describeEventSubscriptionsRequest -
      Returns:
      A Java Future containing the result of the DescribeEventSubscriptions operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SubscriptionNotFoundException The designated subscription could not be found.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeEventSubscriptions

      default CompletableFuture<DescribeEventSubscriptionsResponse> describeEventSubscriptions(Consumer<DescribeEventSubscriptionsRequest.Builder> describeEventSubscriptionsRequest)

      Lists all the subscription descriptions for a customer account. The description for a subscription includes SubscriptionName, SNSTopicARN, CustomerID, SourceType, SourceID, CreationTime, and Status.

      If you specify a SubscriptionName, lists the description for that subscription.


      This is a convenience which creates an instance of the DescribeEventSubscriptionsRequest.Builder avoiding the need to create one manually via DescribeEventSubscriptionsRequest.builder()

      Parameters:
      describeEventSubscriptionsRequest - A Consumer that will call methods on DescribeEventSubscriptionsRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DescribeEventSubscriptions operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SubscriptionNotFoundException The designated subscription could not be found.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeEventSubscriptions

      default CompletableFuture<DescribeEventSubscriptionsResponse> describeEventSubscriptions()

      Lists all the subscription descriptions for a customer account. The description for a subscription includes SubscriptionName, SNSTopicARN, CustomerID, SourceType, SourceID, CreationTime, and Status.

      If you specify a SubscriptionName, lists the description for that subscription.

      Returns:
      A Java Future containing the result of the DescribeEventSubscriptions operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SubscriptionNotFoundException The designated subscription could not be found.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeEventSubscriptionsPaginator

      default DescribeEventSubscriptionsPublisher describeEventSubscriptionsPaginator()

      This is a variant of describeEventSubscriptions(software.amazon.awssdk.services.neptune.model.DescribeEventSubscriptionsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeEventSubscriptionsPublisher publisher = client.describeEventSubscriptionsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeEventSubscriptionsPublisher publisher = client.describeEventSubscriptionsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeEventSubscriptionsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeEventSubscriptionsResponse 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 MaxRecords 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 describeEventSubscriptions(software.amazon.awssdk.services.neptune.model.DescribeEventSubscriptionsRequest) operation.

      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SubscriptionNotFoundException The designated subscription could not be found.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeEventSubscriptionsPaginator

      default DescribeEventSubscriptionsPublisher describeEventSubscriptionsPaginator(DescribeEventSubscriptionsRequest describeEventSubscriptionsRequest)

      This is a variant of describeEventSubscriptions(software.amazon.awssdk.services.neptune.model.DescribeEventSubscriptionsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeEventSubscriptionsPublisher publisher = client.describeEventSubscriptionsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeEventSubscriptionsPublisher publisher = client.describeEventSubscriptionsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeEventSubscriptionsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeEventSubscriptionsResponse 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 MaxRecords 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 describeEventSubscriptions(software.amazon.awssdk.services.neptune.model.DescribeEventSubscriptionsRequest) operation.

      Parameters:
      describeEventSubscriptionsRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SubscriptionNotFoundException The designated subscription could not be found.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeEventSubscriptionsPaginator

      default DescribeEventSubscriptionsPublisher describeEventSubscriptionsPaginator(Consumer<DescribeEventSubscriptionsRequest.Builder> describeEventSubscriptionsRequest)

      This is a variant of describeEventSubscriptions(software.amazon.awssdk.services.neptune.model.DescribeEventSubscriptionsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeEventSubscriptionsPublisher publisher = client.describeEventSubscriptionsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeEventSubscriptionsPublisher publisher = client.describeEventSubscriptionsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeEventSubscriptionsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeEventSubscriptionsResponse 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 MaxRecords 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 describeEventSubscriptions(software.amazon.awssdk.services.neptune.model.DescribeEventSubscriptionsRequest) operation.


      This is a convenience which creates an instance of the DescribeEventSubscriptionsRequest.Builder avoiding the need to create one manually via DescribeEventSubscriptionsRequest.builder()

      Parameters:
      describeEventSubscriptionsRequest - A Consumer that will call methods on DescribeEventSubscriptionsRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SubscriptionNotFoundException The designated subscription could not be found.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeEvents

      default CompletableFuture<DescribeEventsResponse> describeEvents(DescribeEventsRequest describeEventsRequest)

      Returns events related to DB instances, DB security groups, DB snapshots, and DB parameter groups for the past 14 days. Events specific to a particular DB instance, DB security group, database snapshot, or DB parameter group can be obtained by providing the name as a parameter. By default, the past hour of events are returned.

      Parameters:
      describeEventsRequest -
      Returns:
      A Java Future containing the result of the DescribeEvents operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeEvents

      default CompletableFuture<DescribeEventsResponse> describeEvents(Consumer<DescribeEventsRequest.Builder> describeEventsRequest)

      Returns events related to DB instances, DB security groups, DB snapshots, and DB parameter groups for the past 14 days. Events specific to a particular DB instance, DB security group, database snapshot, or DB parameter group can be obtained by providing the name as a parameter. By default, the past hour of events are returned.


      This is a convenience which creates an instance of the DescribeEventsRequest.Builder avoiding the need to create one manually via DescribeEventsRequest.builder()

      Parameters:
      describeEventsRequest - A Consumer that will call methods on DescribeEventsRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DescribeEvents operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeEvents

      default CompletableFuture<DescribeEventsResponse> describeEvents()

      Returns events related to DB instances, DB security groups, DB snapshots, and DB parameter groups for the past 14 days. Events specific to a particular DB instance, DB security group, database snapshot, or DB parameter group can be obtained by providing the name as a parameter. By default, the past hour of events are returned.

      Returns:
      A Java Future containing the result of the DescribeEvents operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeEventsPaginator

      default DescribeEventsPublisher describeEventsPaginator()

      This is a variant of describeEvents(software.amazon.awssdk.services.neptune.model.DescribeEventsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeEventsPublisher publisher = client.describeEventsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeEventsPublisher publisher = client.describeEventsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeEventsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeEventsResponse 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 MaxRecords 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 describeEvents(software.amazon.awssdk.services.neptune.model.DescribeEventsRequest) operation.

      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeEventsPaginator

      default DescribeEventsPublisher describeEventsPaginator(DescribeEventsRequest describeEventsRequest)

      This is a variant of describeEvents(software.amazon.awssdk.services.neptune.model.DescribeEventsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeEventsPublisher publisher = client.describeEventsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeEventsPublisher publisher = client.describeEventsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeEventsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeEventsResponse 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 MaxRecords 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 describeEvents(software.amazon.awssdk.services.neptune.model.DescribeEventsRequest) operation.

      Parameters:
      describeEventsRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeEventsPaginator

      default DescribeEventsPublisher describeEventsPaginator(Consumer<DescribeEventsRequest.Builder> describeEventsRequest)

      This is a variant of describeEvents(software.amazon.awssdk.services.neptune.model.DescribeEventsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeEventsPublisher publisher = client.describeEventsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeEventsPublisher publisher = client.describeEventsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeEventsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeEventsResponse 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 MaxRecords 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 describeEvents(software.amazon.awssdk.services.neptune.model.DescribeEventsRequest) operation.


      This is a convenience which creates an instance of the DescribeEventsRequest.Builder avoiding the need to create one manually via DescribeEventsRequest.builder()

      Parameters:
      describeEventsRequest - A Consumer that will call methods on DescribeEventsRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeGlobalClusters

      default CompletableFuture<DescribeGlobalClustersResponse> describeGlobalClusters(DescribeGlobalClustersRequest describeGlobalClustersRequest)

      Returns information about Neptune global database clusters. This API supports pagination.

      Parameters:
      describeGlobalClustersRequest -
      Returns:
      A Java Future containing the result of the DescribeGlobalClusters operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • GlobalClusterNotFoundException The GlobalClusterIdentifier doesn't refer to an existing global database cluster.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeGlobalClusters

      default CompletableFuture<DescribeGlobalClustersResponse> describeGlobalClusters(Consumer<DescribeGlobalClustersRequest.Builder> describeGlobalClustersRequest)

      Returns information about Neptune global database clusters. This API supports pagination.


      This is a convenience which creates an instance of the DescribeGlobalClustersRequest.Builder avoiding the need to create one manually via DescribeGlobalClustersRequest.builder()

      Parameters:
      describeGlobalClustersRequest - A Consumer that will call methods on DescribeGlobalClustersRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DescribeGlobalClusters operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • GlobalClusterNotFoundException The GlobalClusterIdentifier doesn't refer to an existing global database cluster.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeGlobalClustersPaginator

      default DescribeGlobalClustersPublisher describeGlobalClustersPaginator(DescribeGlobalClustersRequest describeGlobalClustersRequest)

      This is a variant of describeGlobalClusters(software.amazon.awssdk.services.neptune.model.DescribeGlobalClustersRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeGlobalClustersPublisher publisher = client.describeGlobalClustersPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeGlobalClustersPublisher publisher = client.describeGlobalClustersPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeGlobalClustersResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeGlobalClustersResponse 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 MaxRecords 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 describeGlobalClusters(software.amazon.awssdk.services.neptune.model.DescribeGlobalClustersRequest) operation.

      Parameters:
      describeGlobalClustersRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • GlobalClusterNotFoundException The GlobalClusterIdentifier doesn't refer to an existing global database cluster.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeGlobalClustersPaginator

      default DescribeGlobalClustersPublisher describeGlobalClustersPaginator(Consumer<DescribeGlobalClustersRequest.Builder> describeGlobalClustersRequest)

      This is a variant of describeGlobalClusters(software.amazon.awssdk.services.neptune.model.DescribeGlobalClustersRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeGlobalClustersPublisher publisher = client.describeGlobalClustersPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeGlobalClustersPublisher publisher = client.describeGlobalClustersPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeGlobalClustersResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeGlobalClustersResponse 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 MaxRecords 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 describeGlobalClusters(software.amazon.awssdk.services.neptune.model.DescribeGlobalClustersRequest) operation.


      This is a convenience which creates an instance of the DescribeGlobalClustersRequest.Builder avoiding the need to create one manually via DescribeGlobalClustersRequest.builder()

      Parameters:
      describeGlobalClustersRequest - A Consumer that will call methods on DescribeGlobalClustersRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • GlobalClusterNotFoundException The GlobalClusterIdentifier doesn't refer to an existing global database cluster.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeOrderableDBInstanceOptions

      default CompletableFuture<DescribeOrderableDbInstanceOptionsResponse> describeOrderableDBInstanceOptions(DescribeOrderableDbInstanceOptionsRequest describeOrderableDbInstanceOptionsRequest)

      Returns a list of orderable DB instance options for the specified engine.

      Parameters:
      describeOrderableDbInstanceOptionsRequest -
      Returns:
      A Java Future containing the result of the DescribeOrderableDBInstanceOptions operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeOrderableDBInstanceOptions

      default CompletableFuture<DescribeOrderableDbInstanceOptionsResponse> describeOrderableDBInstanceOptions(Consumer<DescribeOrderableDbInstanceOptionsRequest.Builder> describeOrderableDbInstanceOptionsRequest)

      Returns a list of orderable DB instance options for the specified engine.


      This is a convenience which creates an instance of the DescribeOrderableDbInstanceOptionsRequest.Builder avoiding the need to create one manually via DescribeOrderableDbInstanceOptionsRequest.builder()

      Parameters:
      describeOrderableDbInstanceOptionsRequest - A Consumer that will call methods on DescribeOrderableDbInstanceOptionsRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DescribeOrderableDBInstanceOptions operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeOrderableDBInstanceOptionsPaginator

      default DescribeOrderableDBInstanceOptionsPublisher describeOrderableDBInstanceOptionsPaginator(DescribeOrderableDbInstanceOptionsRequest describeOrderableDbInstanceOptionsRequest)

      This is a variant of describeOrderableDBInstanceOptions(software.amazon.awssdk.services.neptune.model.DescribeOrderableDbInstanceOptionsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeOrderableDBInstanceOptionsPublisher publisher = client.describeOrderableDBInstanceOptionsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeOrderableDBInstanceOptionsPublisher publisher = client.describeOrderableDBInstanceOptionsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeOrderableDbInstanceOptionsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeOrderableDbInstanceOptionsResponse 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 MaxRecords 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 describeOrderableDBInstanceOptions(software.amazon.awssdk.services.neptune.model.DescribeOrderableDbInstanceOptionsRequest) operation.

      Parameters:
      describeOrderableDbInstanceOptionsRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeOrderableDBInstanceOptionsPaginator

      default DescribeOrderableDBInstanceOptionsPublisher describeOrderableDBInstanceOptionsPaginator(Consumer<DescribeOrderableDbInstanceOptionsRequest.Builder> describeOrderableDbInstanceOptionsRequest)

      This is a variant of describeOrderableDBInstanceOptions(software.amazon.awssdk.services.neptune.model.DescribeOrderableDbInstanceOptionsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribeOrderableDBInstanceOptionsPublisher publisher = client.describeOrderableDBInstanceOptionsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribeOrderableDBInstanceOptionsPublisher publisher = client.describeOrderableDBInstanceOptionsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribeOrderableDbInstanceOptionsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribeOrderableDbInstanceOptionsResponse 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 MaxRecords 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 describeOrderableDBInstanceOptions(software.amazon.awssdk.services.neptune.model.DescribeOrderableDbInstanceOptionsRequest) operation.


      This is a convenience which creates an instance of the DescribeOrderableDbInstanceOptionsRequest.Builder avoiding the need to create one manually via DescribeOrderableDbInstanceOptionsRequest.builder()

      Parameters:
      describeOrderableDbInstanceOptionsRequest - A Consumer that will call methods on DescribeOrderableDbInstanceOptionsRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describePendingMaintenanceActions

      default CompletableFuture<DescribePendingMaintenanceActionsResponse> describePendingMaintenanceActions(DescribePendingMaintenanceActionsRequest describePendingMaintenanceActionsRequest)

      Returns a list of resources (for example, DB instances) that have at least one pending maintenance action.

      Parameters:
      describePendingMaintenanceActionsRequest -
      Returns:
      A Java Future containing the result of the DescribePendingMaintenanceActions operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ResourceNotFoundException The specified resource ID was not found.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describePendingMaintenanceActions

      default CompletableFuture<DescribePendingMaintenanceActionsResponse> describePendingMaintenanceActions(Consumer<DescribePendingMaintenanceActionsRequest.Builder> describePendingMaintenanceActionsRequest)

      Returns a list of resources (for example, DB instances) that have at least one pending maintenance action.


      This is a convenience which creates an instance of the DescribePendingMaintenanceActionsRequest.Builder avoiding the need to create one manually via DescribePendingMaintenanceActionsRequest.builder()

      Parameters:
      describePendingMaintenanceActionsRequest - A Consumer that will call methods on DescribePendingMaintenanceActionsRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DescribePendingMaintenanceActions operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ResourceNotFoundException The specified resource ID was not found.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describePendingMaintenanceActions

      default CompletableFuture<DescribePendingMaintenanceActionsResponse> describePendingMaintenanceActions()

      Returns a list of resources (for example, DB instances) that have at least one pending maintenance action.

      Returns:
      A Java Future containing the result of the DescribePendingMaintenanceActions operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ResourceNotFoundException The specified resource ID was not found.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describePendingMaintenanceActionsPaginator

      default DescribePendingMaintenanceActionsPublisher describePendingMaintenanceActionsPaginator()

      This is a variant of describePendingMaintenanceActions(software.amazon.awssdk.services.neptune.model.DescribePendingMaintenanceActionsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribePendingMaintenanceActionsPublisher publisher = client.describePendingMaintenanceActionsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribePendingMaintenanceActionsPublisher publisher = client.describePendingMaintenanceActionsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribePendingMaintenanceActionsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribePendingMaintenanceActionsResponse 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 MaxRecords 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 describePendingMaintenanceActions(software.amazon.awssdk.services.neptune.model.DescribePendingMaintenanceActionsRequest) operation.

      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ResourceNotFoundException The specified resource ID was not found.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describePendingMaintenanceActionsPaginator

      default DescribePendingMaintenanceActionsPublisher describePendingMaintenanceActionsPaginator(DescribePendingMaintenanceActionsRequest describePendingMaintenanceActionsRequest)

      This is a variant of describePendingMaintenanceActions(software.amazon.awssdk.services.neptune.model.DescribePendingMaintenanceActionsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribePendingMaintenanceActionsPublisher publisher = client.describePendingMaintenanceActionsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribePendingMaintenanceActionsPublisher publisher = client.describePendingMaintenanceActionsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribePendingMaintenanceActionsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribePendingMaintenanceActionsResponse 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 MaxRecords 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 describePendingMaintenanceActions(software.amazon.awssdk.services.neptune.model.DescribePendingMaintenanceActionsRequest) operation.

      Parameters:
      describePendingMaintenanceActionsRequest -
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ResourceNotFoundException The specified resource ID was not found.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describePendingMaintenanceActionsPaginator

      default DescribePendingMaintenanceActionsPublisher describePendingMaintenanceActionsPaginator(Consumer<DescribePendingMaintenanceActionsRequest.Builder> describePendingMaintenanceActionsRequest)

      This is a variant of describePendingMaintenanceActions(software.amazon.awssdk.services.neptune.model.DescribePendingMaintenanceActionsRequest) operation. The return type is a custom publisher that can be subscribed to request a stream of response pages. SDK will internally handle making service calls for you.

      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.neptune.paginators.DescribePendingMaintenanceActionsPublisher publisher = client.describePendingMaintenanceActionsPaginator(request);
 CompletableFuture<Void> future = publisher.subscribe(res -> { // Do something with the response });
 future.get();
      2) Using a custom subscriber 
       
 software.amazon.awssdk.services.neptune.paginators.DescribePendingMaintenanceActionsPublisher publisher = client.describePendingMaintenanceActionsPaginator(request);
 publisher.subscribe(new Subscriber<software.amazon.awssdk.services.neptune.model.DescribePendingMaintenanceActionsResponse>() {
 
 public void onSubscribe(org.reactivestreams.Subscriber subscription) { //... };
 
 
 public void onNext(software.amazon.awssdk.services.neptune.model.DescribePendingMaintenanceActionsResponse 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 MaxRecords 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 describePendingMaintenanceActions(software.amazon.awssdk.services.neptune.model.DescribePendingMaintenanceActionsRequest) operation.


      This is a convenience which creates an instance of the DescribePendingMaintenanceActionsRequest.Builder avoiding the need to create one manually via DescribePendingMaintenanceActionsRequest.builder()

      Parameters:
      describePendingMaintenanceActionsRequest - A Consumer that will call methods on DescribePendingMaintenanceActionsRequest.Builder to create a request.
      Returns:
      A custom publisher that can be subscribed to request a stream of response pages.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • ResourceNotFoundException The specified resource ID was not found.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeValidDBInstanceModifications

      default CompletableFuture<DescribeValidDbInstanceModificationsResponse> describeValidDBInstanceModifications(DescribeValidDbInstanceModificationsRequest describeValidDbInstanceModificationsRequest)

      You can call DescribeValidDBInstanceModifications to learn what modifications you can make to your DB instance. You can use this information when you call ModifyDBInstance.

      Parameters:
      describeValidDbInstanceModificationsRequest -
      Returns:
      A Java Future containing the result of the DescribeValidDBInstanceModifications operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbInstanceNotFoundException DBInstanceIdentifier does not refer to an existing DB instance.
      • InvalidDbInstanceStateException The specified DB instance is not in the available state.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • describeValidDBInstanceModifications

      default CompletableFuture<DescribeValidDbInstanceModificationsResponse> describeValidDBInstanceModifications(Consumer<DescribeValidDbInstanceModificationsRequest.Builder> describeValidDbInstanceModificationsRequest)

      You can call DescribeValidDBInstanceModifications to learn what modifications you can make to your DB instance. You can use this information when you call ModifyDBInstance.


      This is a convenience which creates an instance of the DescribeValidDbInstanceModificationsRequest.Builder avoiding the need to create one manually via DescribeValidDbInstanceModificationsRequest.builder()

      Parameters:
      describeValidDbInstanceModificationsRequest - A Consumer that will call methods on DescribeValidDbInstanceModificationsRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the DescribeValidDBInstanceModifications operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbInstanceNotFoundException DBInstanceIdentifier does not refer to an existing DB instance.
      • InvalidDbInstanceStateException The specified DB instance is not in the available state.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • failoverDBCluster

      default CompletableFuture<FailoverDbClusterResponse> failoverDBCluster(FailoverDbClusterRequest failoverDbClusterRequest)

      Forces a failover for a DB cluster.

      A failover for a DB cluster promotes one of the Read Replicas (read-only instances) in the DB cluster to be the primary instance (the cluster writer).

      Amazon Neptune will automatically fail over to a Read Replica, if one exists, when the primary instance fails. You can force a failover when you want to simulate a failure of a primary instance for testing. Because each instance in a DB cluster has its own endpoint address, you will need to clean up and re-establish any existing connections that use those endpoint addresses when the failover is complete.

      Parameters:
      failoverDbClusterRequest -
      Returns:
      A Java Future containing the result of the FailoverDBCluster operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • InvalidDbInstanceStateException The specified DB instance is not in the available state.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • failoverDBCluster

      default CompletableFuture<FailoverDbClusterResponse> failoverDBCluster(Consumer<FailoverDbClusterRequest.Builder> failoverDbClusterRequest)

      Forces a failover for a DB cluster.

      A failover for a DB cluster promotes one of the Read Replicas (read-only instances) in the DB cluster to be the primary instance (the cluster writer).

      Amazon Neptune will automatically fail over to a Read Replica, if one exists, when the primary instance fails. You can force a failover when you want to simulate a failure of a primary instance for testing. Because each instance in a DB cluster has its own endpoint address, you will need to clean up and re-establish any existing connections that use those endpoint addresses when the failover is complete.


      This is a convenience which creates an instance of the FailoverDbClusterRequest.Builder avoiding the need to create one manually via FailoverDbClusterRequest.builder()

      Parameters:
      failoverDbClusterRequest - A Consumer that will call methods on FailoverDbClusterRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the FailoverDBCluster operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • InvalidDbInstanceStateException The specified DB instance is not in the available state.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • failoverGlobalCluster

      default CompletableFuture<FailoverGlobalClusterResponse> failoverGlobalCluster(FailoverGlobalClusterRequest failoverGlobalClusterRequest)

      Initiates the failover process for a Neptune global database.

      A failover for a Neptune global database promotes one of secondary read-only DB clusters to be the primary DB cluster and demotes the primary DB cluster to being a secondary (read-only) DB cluster. In other words, the role of the current primary DB cluster and the selected target secondary DB cluster are switched. The selected secondary DB cluster assumes full read/write capabilities for the Neptune global database.

      This action applies only to Neptune global databases. This action is only intended for use on healthy Neptune global databases with healthy Neptune DB clusters and no region-wide outages, to test disaster recovery scenarios or to reconfigure the global database topology.

      Parameters:
      failoverGlobalClusterRequest -
      Returns:
      A Java Future containing the result of the FailoverGlobalCluster operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • GlobalClusterNotFoundException The GlobalClusterIdentifier doesn't refer to an existing global database cluster.
      • InvalidGlobalClusterStateException The global cluster is in an invalid state and can't perform the requested operation.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • failoverGlobalCluster

      default CompletableFuture<FailoverGlobalClusterResponse> failoverGlobalCluster(Consumer<FailoverGlobalClusterRequest.Builder> failoverGlobalClusterRequest)

      Initiates the failover process for a Neptune global database.

      A failover for a Neptune global database promotes one of secondary read-only DB clusters to be the primary DB cluster and demotes the primary DB cluster to being a secondary (read-only) DB cluster. In other words, the role of the current primary DB cluster and the selected target secondary DB cluster are switched. The selected secondary DB cluster assumes full read/write capabilities for the Neptune global database.

      This action applies only to Neptune global databases. This action is only intended for use on healthy Neptune global databases with healthy Neptune DB clusters and no region-wide outages, to test disaster recovery scenarios or to reconfigure the global database topology.


      This is a convenience which creates an instance of the FailoverGlobalClusterRequest.Builder avoiding the need to create one manually via FailoverGlobalClusterRequest.builder()

      Parameters:
      failoverGlobalClusterRequest - A Consumer that will call methods on FailoverGlobalClusterRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the FailoverGlobalCluster operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • GlobalClusterNotFoundException The GlobalClusterIdentifier doesn't refer to an existing global database cluster.
      • InvalidGlobalClusterStateException The global cluster is in an invalid state and can't perform the requested operation.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listTagsForResource

      default CompletableFuture<ListTagsForResourceResponse> listTagsForResource(ListTagsForResourceRequest listTagsForResourceRequest)

      Lists all tags on an Amazon Neptune resource.

      Parameters:
      listTagsForResourceRequest -
      Returns:
      A Java Future containing the result of the ListTagsForResource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbInstanceNotFoundException DBInstanceIdentifier does not refer to an existing DB instance.
      • DbSnapshotNotFoundException DBSnapshotIdentifier does not refer to an existing DB snapshot.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • listTagsForResource

      default CompletableFuture<ListTagsForResourceResponse> listTagsForResource(Consumer<ListTagsForResourceRequest.Builder> listTagsForResourceRequest)

      Lists all tags on an Amazon Neptune resource.


      This is a convenience which creates an instance of the ListTagsForResourceRequest.Builder avoiding the need to create one manually via ListTagsForResourceRequest.builder()

      Parameters:
      listTagsForResourceRequest - A Consumer that will call methods on ListTagsForResourceRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ListTagsForResource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbInstanceNotFoundException DBInstanceIdentifier does not refer to an existing DB instance.
      • DbSnapshotNotFoundException DBSnapshotIdentifier does not refer to an existing DB snapshot.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • modifyDBCluster

      default CompletableFuture<ModifyDbClusterResponse> modifyDBCluster(ModifyDbClusterRequest modifyDbClusterRequest)

      Modify a setting for a DB cluster. You can change one or more database configuration parameters by specifying these parameters and the new values in the request.

      Parameters:
      modifyDbClusterRequest -
      Returns:
      A Java Future containing the result of the ModifyDBCluster operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • StorageQuotaExceededException Request would result in user exceeding the allowed amount of storage available across all DB instances.
      • DbSubnetGroupNotFoundException DBSubnetGroupName does not refer to an existing DB subnet group.
      • InvalidVpcNetworkStateException DB subnet group does not cover all Availability Zones after it is created because users' change.
      • InvalidDbSubnetGroupStateException The DB subnet group cannot be deleted because it is in use.
      • InvalidSubnetException The requested subnet is invalid, or multiple subnets were requested that are not all in a common VPC.
      • DbClusterParameterGroupNotFoundException DBClusterParameterGroupName does not refer to an existing DB Cluster parameter group.
      • InvalidDbSecurityGroupStateException The state of the DB security group does not allow deletion.
      • InvalidDbInstanceStateException The specified DB instance is not in the available state.
      • DbClusterAlreadyExistsException User already has a DB cluster with the given identifier.
      • StorageTypeNotSupportedException StorageType specified cannot be associated with the DB Instance.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • modifyDBCluster

      default CompletableFuture<ModifyDbClusterResponse> modifyDBCluster(Consumer<ModifyDbClusterRequest.Builder> modifyDbClusterRequest)

      Modify a setting for a DB cluster. You can change one or more database configuration parameters by specifying these parameters and the new values in the request.


      This is a convenience which creates an instance of the ModifyDbClusterRequest.Builder avoiding the need to create one manually via ModifyDbClusterRequest.builder()

      Parameters:
      modifyDbClusterRequest - A Consumer that will call methods on ModifyDbClusterRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ModifyDBCluster operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • StorageQuotaExceededException Request would result in user exceeding the allowed amount of storage available across all DB instances.
      • DbSubnetGroupNotFoundException DBSubnetGroupName does not refer to an existing DB subnet group.
      • InvalidVpcNetworkStateException DB subnet group does not cover all Availability Zones after it is created because users' change.
      • InvalidDbSubnetGroupStateException The DB subnet group cannot be deleted because it is in use.
      • InvalidSubnetException The requested subnet is invalid, or multiple subnets were requested that are not all in a common VPC.
      • DbClusterParameterGroupNotFoundException DBClusterParameterGroupName does not refer to an existing DB Cluster parameter group.
      • InvalidDbSecurityGroupStateException The state of the DB security group does not allow deletion.
      • InvalidDbInstanceStateException The specified DB instance is not in the available state.
      • DbClusterAlreadyExistsException User already has a DB cluster with the given identifier.
      • StorageTypeNotSupportedException StorageType specified cannot be associated with the DB Instance.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • modifyDBClusterEndpoint

      default CompletableFuture<ModifyDbClusterEndpointResponse> modifyDBClusterEndpoint(ModifyDbClusterEndpointRequest modifyDbClusterEndpointRequest)

      Modifies the properties of an endpoint in an Amazon Neptune DB cluster.

      Parameters:
      modifyDbClusterEndpointRequest -
      Returns:
      A Java Future containing the result of the ModifyDBClusterEndpoint operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • InvalidDbClusterEndpointStateException The requested operation cannot be performed on the endpoint while the endpoint is in this state.
      • DbClusterEndpointNotFoundException The specified custom endpoint doesn't exist.
      • DbInstanceNotFoundException DBInstanceIdentifier does not refer to an existing DB instance.
      • InvalidDbInstanceStateException The specified DB instance is not in the available state.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • modifyDBClusterEndpoint

      default CompletableFuture<ModifyDbClusterEndpointResponse> modifyDBClusterEndpoint(Consumer<ModifyDbClusterEndpointRequest.Builder> modifyDbClusterEndpointRequest)

      Modifies the properties of an endpoint in an Amazon Neptune DB cluster.


      This is a convenience which creates an instance of the ModifyDbClusterEndpointRequest.Builder avoiding the need to create one manually via ModifyDbClusterEndpointRequest.builder()

      Parameters:
      modifyDbClusterEndpointRequest - A Consumer that will call methods on ModifyDbClusterEndpointRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ModifyDBClusterEndpoint operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • InvalidDbClusterEndpointStateException The requested operation cannot be performed on the endpoint while the endpoint is in this state.
      • DbClusterEndpointNotFoundException The specified custom endpoint doesn't exist.
      • DbInstanceNotFoundException DBInstanceIdentifier does not refer to an existing DB instance.
      • InvalidDbInstanceStateException The specified DB instance is not in the available state.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • modifyDBClusterParameterGroup

      default CompletableFuture<ModifyDbClusterParameterGroupResponse> modifyDBClusterParameterGroup(ModifyDbClusterParameterGroupRequest modifyDbClusterParameterGroupRequest)

      Modifies the parameters of a DB cluster parameter group. To modify more than one parameter, submit a list of the following: ParameterName, ParameterValue, and ApplyMethod. A maximum of 20 parameters can be modified in a single request.

      Changes to dynamic parameters are applied immediately. Changes to static parameters require a reboot without failover to the DB cluster associated with the parameter group before the change can take effect.

      After you create a DB cluster parameter group, you should wait at least 5 minutes before creating your first DB cluster that uses that DB cluster parameter group as the default parameter group. This allows Amazon Neptune to fully complete the create action before the parameter group is used as the default for a new DB cluster. This is especially important for parameters that are critical when creating the default database for a DB cluster, such as the character set for the default database defined by the character_set_database parameter. You can use the Parameter Groups option of the Amazon Neptune console or the DescribeDBClusterParameters command to verify that your DB cluster parameter group has been created or modified.

      Parameters:
      modifyDbClusterParameterGroupRequest -
      Returns:
      A Java Future containing the result of the ModifyDBClusterParameterGroup operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • InvalidDbParameterGroupStateException The DB parameter group is in use or is in an invalid state. If you are attempting to delete the parameter group, you cannot delete it when the parameter group is in this state.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • modifyDBClusterParameterGroup

      default CompletableFuture<ModifyDbClusterParameterGroupResponse> modifyDBClusterParameterGroup(Consumer<ModifyDbClusterParameterGroupRequest.Builder> modifyDbClusterParameterGroupRequest)

      Modifies the parameters of a DB cluster parameter group. To modify more than one parameter, submit a list of the following: ParameterName, ParameterValue, and ApplyMethod. A maximum of 20 parameters can be modified in a single request.

      Changes to dynamic parameters are applied immediately. Changes to static parameters require a reboot without failover to the DB cluster associated with the parameter group before the change can take effect.

      After you create a DB cluster parameter group, you should wait at least 5 minutes before creating your first DB cluster that uses that DB cluster parameter group as the default parameter group. This allows Amazon Neptune to fully complete the create action before the parameter group is used as the default for a new DB cluster. This is especially important for parameters that are critical when creating the default database for a DB cluster, such as the character set for the default database defined by the character_set_database parameter. You can use the Parameter Groups option of the Amazon Neptune console or the DescribeDBClusterParameters command to verify that your DB cluster parameter group has been created or modified.


      This is a convenience which creates an instance of the ModifyDbClusterParameterGroupRequest.Builder avoiding the need to create one manually via ModifyDbClusterParameterGroupRequest.builder()

      Parameters:
      modifyDbClusterParameterGroupRequest - A Consumer that will call methods on ModifyDbClusterParameterGroupRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ModifyDBClusterParameterGroup operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • InvalidDbParameterGroupStateException The DB parameter group is in use or is in an invalid state. If you are attempting to delete the parameter group, you cannot delete it when the parameter group is in this state.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • modifyDBClusterSnapshotAttribute

      default CompletableFuture<ModifyDbClusterSnapshotAttributeResponse> modifyDBClusterSnapshotAttribute(ModifyDbClusterSnapshotAttributeRequest modifyDbClusterSnapshotAttributeRequest)

      Adds an attribute and values to, or removes an attribute and values from, a manual DB cluster snapshot.

      To share a manual DB cluster snapshot with other Amazon accounts, specify restore as the AttributeName and use the ValuesToAdd parameter to add a list of IDs of the Amazon accounts that are authorized to restore the manual DB cluster snapshot. Use the value all to make the manual DB cluster snapshot public, which means that it can be copied or restored by all Amazon accounts. Do not add the all value for any manual DB cluster snapshots that contain private information that you don't want available to all Amazon accounts. If a manual DB cluster snapshot is encrypted, it can be shared, but only by specifying a list of authorized Amazon account IDs for the ValuesToAdd parameter. You can't use all as a value for that parameter in this case.

      To view which Amazon accounts have access to copy or restore a manual DB cluster snapshot, or whether a manual DB cluster snapshot public or private, use the DescribeDBClusterSnapshotAttributes API action.

      Parameters:
      modifyDbClusterSnapshotAttributeRequest -
      Returns:
      A Java Future containing the result of the ModifyDBClusterSnapshotAttribute operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterSnapshotNotFoundException DBClusterSnapshotIdentifier does not refer to an existing DB cluster snapshot.
      • InvalidDbClusterSnapshotStateException The supplied value is not a valid DB cluster snapshot state.
      • SharedSnapshotQuotaExceededException You have exceeded the maximum number of accounts that you can share a manual DB snapshot with.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • modifyDBClusterSnapshotAttribute

      default CompletableFuture<ModifyDbClusterSnapshotAttributeResponse> modifyDBClusterSnapshotAttribute(Consumer<ModifyDbClusterSnapshotAttributeRequest.Builder> modifyDbClusterSnapshotAttributeRequest)

      Adds an attribute and values to, or removes an attribute and values from, a manual DB cluster snapshot.

      To share a manual DB cluster snapshot with other Amazon accounts, specify restore as the AttributeName and use the ValuesToAdd parameter to add a list of IDs of the Amazon accounts that are authorized to restore the manual DB cluster snapshot. Use the value all to make the manual DB cluster snapshot public, which means that it can be copied or restored by all Amazon accounts. Do not add the all value for any manual DB cluster snapshots that contain private information that you don't want available to all Amazon accounts. If a manual DB cluster snapshot is encrypted, it can be shared, but only by specifying a list of authorized Amazon account IDs for the ValuesToAdd parameter. You can't use all as a value for that parameter in this case.

      To view which Amazon accounts have access to copy or restore a manual DB cluster snapshot, or whether a manual DB cluster snapshot public or private, use the DescribeDBClusterSnapshotAttributes API action.


      This is a convenience which creates an instance of the ModifyDbClusterSnapshotAttributeRequest.Builder avoiding the need to create one manually via ModifyDbClusterSnapshotAttributeRequest.builder()

      Parameters:
      modifyDbClusterSnapshotAttributeRequest - A Consumer that will call methods on ModifyDbClusterSnapshotAttributeRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ModifyDBClusterSnapshotAttribute operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterSnapshotNotFoundException DBClusterSnapshotIdentifier does not refer to an existing DB cluster snapshot.
      • InvalidDbClusterSnapshotStateException The supplied value is not a valid DB cluster snapshot state.
      • SharedSnapshotQuotaExceededException You have exceeded the maximum number of accounts that you can share a manual DB snapshot with.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • modifyDBInstance

      default CompletableFuture<ModifyDbInstanceResponse> modifyDBInstance(ModifyDbInstanceRequest modifyDbInstanceRequest)

      Modifies settings for a DB instance. You can change one or more database configuration parameters by specifying these parameters and the new values in the request. To learn what modifications you can make to your DB instance, call DescribeValidDBInstanceModifications before you call ModifyDBInstance.

      Parameters:
      modifyDbInstanceRequest -
      Returns:
      A Java Future containing the result of the ModifyDBInstance operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidDbInstanceStateException The specified DB instance is not in the available state.
      • InvalidDbSecurityGroupStateException The state of the DB security group does not allow deletion.
      • DbInstanceAlreadyExistsException User already has a DB instance with the given identifier.
      • DbInstanceNotFoundException DBInstanceIdentifier does not refer to an existing DB instance.
      • DbSecurityGroupNotFoundException DBSecurityGroupName does not refer to an existing DB security group.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • InsufficientDbInstanceCapacityException Specified DB instance class is not available in the specified Availability Zone.
      • StorageQuotaExceededException Request would result in user exceeding the allowed amount of storage available across all DB instances.
      • InvalidVpcNetworkStateException DB subnet group does not cover all Availability Zones after it is created because users' change.
      • ProvisionedIopsNotAvailableInAzException Provisioned IOPS not available in the specified Availability Zone.
      • OptionGroupNotFoundException The designated option group could not be found.
      • DbUpgradeDependencyFailureException The DB upgrade failed because a resource the DB depends on could not be modified.
      • StorageTypeNotSupportedException StorageType specified cannot be associated with the DB Instance.
      • AuthorizationNotFoundException Specified CIDRIP or EC2 security group is not authorized for the specified DB security group.

        Neptune may not also be authorized via IAM to perform necessary actions on your behalf.

      • CertificateNotFoundException CertificateIdentifier does not refer to an existing certificate.
      • DomainNotFoundException Domain does not refer to an existing Active Directory Domain.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • modifyDBInstance

      default CompletableFuture<ModifyDbInstanceResponse> modifyDBInstance(Consumer<ModifyDbInstanceRequest.Builder> modifyDbInstanceRequest)

      Modifies settings for a DB instance. You can change one or more database configuration parameters by specifying these parameters and the new values in the request. To learn what modifications you can make to your DB instance, call DescribeValidDBInstanceModifications before you call ModifyDBInstance.


      This is a convenience which creates an instance of the ModifyDbInstanceRequest.Builder avoiding the need to create one manually via ModifyDbInstanceRequest.builder()

      Parameters:
      modifyDbInstanceRequest - A Consumer that will call methods on ModifyDbInstanceRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ModifyDBInstance operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidDbInstanceStateException The specified DB instance is not in the available state.
      • InvalidDbSecurityGroupStateException The state of the DB security group does not allow deletion.
      • DbInstanceAlreadyExistsException User already has a DB instance with the given identifier.
      • DbInstanceNotFoundException DBInstanceIdentifier does not refer to an existing DB instance.
      • DbSecurityGroupNotFoundException DBSecurityGroupName does not refer to an existing DB security group.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • InsufficientDbInstanceCapacityException Specified DB instance class is not available in the specified Availability Zone.
      • StorageQuotaExceededException Request would result in user exceeding the allowed amount of storage available across all DB instances.
      • InvalidVpcNetworkStateException DB subnet group does not cover all Availability Zones after it is created because users' change.
      • ProvisionedIopsNotAvailableInAzException Provisioned IOPS not available in the specified Availability Zone.
      • OptionGroupNotFoundException The designated option group could not be found.
      • DbUpgradeDependencyFailureException The DB upgrade failed because a resource the DB depends on could not be modified.
      • StorageTypeNotSupportedException StorageType specified cannot be associated with the DB Instance.
      • AuthorizationNotFoundException Specified CIDRIP or EC2 security group is not authorized for the specified DB security group.

        Neptune may not also be authorized via IAM to perform necessary actions on your behalf.

      • CertificateNotFoundException CertificateIdentifier does not refer to an existing certificate.
      • DomainNotFoundException Domain does not refer to an existing Active Directory Domain.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • modifyDBParameterGroup

      default CompletableFuture<ModifyDbParameterGroupResponse> modifyDBParameterGroup(ModifyDbParameterGroupRequest modifyDbParameterGroupRequest)

      Modifies the parameters of a DB parameter group. To modify more than one parameter, submit a list of the following: ParameterName, ParameterValue, and ApplyMethod. A maximum of 20 parameters can be modified in a single request.

      Changes to dynamic parameters are applied immediately. Changes to static parameters require a reboot without failover to the DB instance associated with the parameter group before the change can take effect.

      After you modify a DB parameter group, you should wait at least 5 minutes before creating your first DB instance that uses that DB parameter group as the default parameter group. This allows Amazon Neptune to fully complete the modify action before the parameter group is used as the default for a new DB instance. This is especially important for parameters that are critical when creating the default database for a DB instance, such as the character set for the default database defined by the character_set_database parameter. You can use the Parameter Groups option of the Amazon Neptune console or the DescribeDBParameters command to verify that your DB parameter group has been created or modified.

      Parameters:
      modifyDbParameterGroupRequest -
      Returns:
      A Java Future containing the result of the ModifyDBParameterGroup operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • InvalidDbParameterGroupStateException The DB parameter group is in use or is in an invalid state. If you are attempting to delete the parameter group, you cannot delete it when the parameter group is in this state.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • modifyDBParameterGroup

      default CompletableFuture<ModifyDbParameterGroupResponse> modifyDBParameterGroup(Consumer<ModifyDbParameterGroupRequest.Builder> modifyDbParameterGroupRequest)

      Modifies the parameters of a DB parameter group. To modify more than one parameter, submit a list of the following: ParameterName, ParameterValue, and ApplyMethod. A maximum of 20 parameters can be modified in a single request.

      Changes to dynamic parameters are applied immediately. Changes to static parameters require a reboot without failover to the DB instance associated with the parameter group before the change can take effect.

      After you modify a DB parameter group, you should wait at least 5 minutes before creating your first DB instance that uses that DB parameter group as the default parameter group. This allows Amazon Neptune to fully complete the modify action before the parameter group is used as the default for a new DB instance. This is especially important for parameters that are critical when creating the default database for a DB instance, such as the character set for the default database defined by the character_set_database parameter. You can use the Parameter Groups option of the Amazon Neptune console or the DescribeDBParameters command to verify that your DB parameter group has been created or modified.


      This is a convenience which creates an instance of the ModifyDbParameterGroupRequest.Builder avoiding the need to create one manually via ModifyDbParameterGroupRequest.builder()

      Parameters:
      modifyDbParameterGroupRequest - A Consumer that will call methods on ModifyDbParameterGroupRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ModifyDBParameterGroup operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • InvalidDbParameterGroupStateException The DB parameter group is in use or is in an invalid state. If you are attempting to delete the parameter group, you cannot delete it when the parameter group is in this state.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • modifyDBSubnetGroup

      default CompletableFuture<ModifyDbSubnetGroupResponse> modifyDBSubnetGroup(ModifyDbSubnetGroupRequest modifyDbSubnetGroupRequest)

      Modifies an existing DB subnet group. DB subnet groups must contain at least one subnet in at least two AZs in the Amazon Region.

      Parameters:
      modifyDbSubnetGroupRequest -
      Returns:
      A Java Future containing the result of the ModifyDBSubnetGroup operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbSubnetGroupNotFoundException DBSubnetGroupName does not refer to an existing DB subnet group.
      • DbSubnetQuotaExceededException Request would result in user exceeding the allowed number of subnets in a DB subnet groups.
      • SubnetAlreadyInUseException The DB subnet is already in use in the Availability Zone.
      • DbSubnetGroupDoesNotCoverEnoughAZsException Subnets in the DB subnet group should cover at least two Availability Zones unless there is only one Availability Zone.
      • InvalidSubnetException The requested subnet is invalid, or multiple subnets were requested that are not all in a common VPC.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • modifyDBSubnetGroup

      default CompletableFuture<ModifyDbSubnetGroupResponse> modifyDBSubnetGroup(Consumer<ModifyDbSubnetGroupRequest.Builder> modifyDbSubnetGroupRequest)

      Modifies an existing DB subnet group. DB subnet groups must contain at least one subnet in at least two AZs in the Amazon Region.


      This is a convenience which creates an instance of the ModifyDbSubnetGroupRequest.Builder avoiding the need to create one manually via ModifyDbSubnetGroupRequest.builder()

      Parameters:
      modifyDbSubnetGroupRequest - A Consumer that will call methods on ModifyDbSubnetGroupRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ModifyDBSubnetGroup operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbSubnetGroupNotFoundException DBSubnetGroupName does not refer to an existing DB subnet group.
      • DbSubnetQuotaExceededException Request would result in user exceeding the allowed number of subnets in a DB subnet groups.
      • SubnetAlreadyInUseException The DB subnet is already in use in the Availability Zone.
      • DbSubnetGroupDoesNotCoverEnoughAZsException Subnets in the DB subnet group should cover at least two Availability Zones unless there is only one Availability Zone.
      • InvalidSubnetException The requested subnet is invalid, or multiple subnets were requested that are not all in a common VPC.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • modifyEventSubscription

      default CompletableFuture<ModifyEventSubscriptionResponse> modifyEventSubscription(ModifyEventSubscriptionRequest modifyEventSubscriptionRequest)

      Modifies an existing event notification subscription. Note that you can't modify the source identifiers using this call; to change source identifiers for a subscription, use the AddSourceIdentifierToSubscription and RemoveSourceIdentifierFromSubscription calls.

      You can see a list of the event categories for a given SourceType by using the DescribeEventCategories action.

      Parameters:
      modifyEventSubscriptionRequest -
      Returns:
      A Java Future containing the result of the ModifyEventSubscription operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • EventSubscriptionQuotaExceededException You have exceeded the number of events you can subscribe to.
      • SubscriptionNotFoundException The designated subscription could not be found.
      • SnsInvalidTopicException The SNS topic is invalid.
      • SnsNoAuthorizationException There is no SNS authorization.
      • SnsTopicArnNotFoundException The ARN of the SNS topic could not be found.
      • SubscriptionCategoryNotFoundException The designated subscription category could not be found.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • modifyEventSubscription

      default CompletableFuture<ModifyEventSubscriptionResponse> modifyEventSubscription(Consumer<ModifyEventSubscriptionRequest.Builder> modifyEventSubscriptionRequest)

      Modifies an existing event notification subscription. Note that you can't modify the source identifiers using this call; to change source identifiers for a subscription, use the AddSourceIdentifierToSubscription and RemoveSourceIdentifierFromSubscription calls.

      You can see a list of the event categories for a given SourceType by using the DescribeEventCategories action.


      This is a convenience which creates an instance of the ModifyEventSubscriptionRequest.Builder avoiding the need to create one manually via ModifyEventSubscriptionRequest.builder()

      Parameters:
      modifyEventSubscriptionRequest - A Consumer that will call methods on ModifyEventSubscriptionRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ModifyEventSubscription operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • EventSubscriptionQuotaExceededException You have exceeded the number of events you can subscribe to.
      • SubscriptionNotFoundException The designated subscription could not be found.
      • SnsInvalidTopicException The SNS topic is invalid.
      • SnsNoAuthorizationException There is no SNS authorization.
      • SnsTopicArnNotFoundException The ARN of the SNS topic could not be found.
      • SubscriptionCategoryNotFoundException The designated subscription category could not be found.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • modifyGlobalCluster

      default CompletableFuture<ModifyGlobalClusterResponse> modifyGlobalCluster(ModifyGlobalClusterRequest modifyGlobalClusterRequest)

      Modify a setting for an Amazon Neptune global cluster. You can change one or more database configuration parameters by specifying these parameters and their new values in the request.

      Parameters:
      modifyGlobalClusterRequest -
      Returns:
      A Java Future containing the result of the ModifyGlobalCluster operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • GlobalClusterNotFoundException The GlobalClusterIdentifier doesn't refer to an existing global database cluster.
      • InvalidGlobalClusterStateException The global cluster is in an invalid state and can't perform the requested operation.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • modifyGlobalCluster

      default CompletableFuture<ModifyGlobalClusterResponse> modifyGlobalCluster(Consumer<ModifyGlobalClusterRequest.Builder> modifyGlobalClusterRequest)

      Modify a setting for an Amazon Neptune global cluster. You can change one or more database configuration parameters by specifying these parameters and their new values in the request.


      This is a convenience which creates an instance of the ModifyGlobalClusterRequest.Builder avoiding the need to create one manually via ModifyGlobalClusterRequest.builder()

      Parameters:
      modifyGlobalClusterRequest - A Consumer that will call methods on ModifyGlobalClusterRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ModifyGlobalCluster operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • GlobalClusterNotFoundException The GlobalClusterIdentifier doesn't refer to an existing global database cluster.
      • InvalidGlobalClusterStateException The global cluster is in an invalid state and can't perform the requested operation.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • promoteReadReplicaDBCluster

      default CompletableFuture<PromoteReadReplicaDbClusterResponse> promoteReadReplicaDBCluster(PromoteReadReplicaDbClusterRequest promoteReadReplicaDbClusterRequest)

      Not supported.

      Parameters:
      promoteReadReplicaDbClusterRequest -
      Returns:
      A Java Future containing the result of the PromoteReadReplicaDBCluster operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • promoteReadReplicaDBCluster

      default CompletableFuture<PromoteReadReplicaDbClusterResponse> promoteReadReplicaDBCluster(Consumer<PromoteReadReplicaDbClusterRequest.Builder> promoteReadReplicaDbClusterRequest)

      Not supported.


      This is a convenience which creates an instance of the PromoteReadReplicaDbClusterRequest.Builder avoiding the need to create one manually via PromoteReadReplicaDbClusterRequest.builder()

      Parameters:
      promoteReadReplicaDbClusterRequest - A Consumer that will call methods on PromoteReadReplicaDbClusterRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the PromoteReadReplicaDBCluster operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • rebootDBInstance

      default CompletableFuture<RebootDbInstanceResponse> rebootDBInstance(RebootDbInstanceRequest rebootDbInstanceRequest)

      You might need to reboot your DB instance, usually for maintenance reasons. For example, if you make certain modifications, or if you change the DB parameter group associated with the DB instance, you must reboot the instance for the changes to take effect.

      Rebooting a DB instance restarts the database engine service. Rebooting a DB instance results in a momentary outage, during which the DB instance status is set to rebooting.

      Parameters:
      rebootDbInstanceRequest -
      Returns:
      A Java Future containing the result of the RebootDBInstance operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidDbInstanceStateException The specified DB instance is not in the available state.
      • DbInstanceNotFoundException DBInstanceIdentifier does not refer to an existing DB instance.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • rebootDBInstance

      default CompletableFuture<RebootDbInstanceResponse> rebootDBInstance(Consumer<RebootDbInstanceRequest.Builder> rebootDbInstanceRequest)

      You might need to reboot your DB instance, usually for maintenance reasons. For example, if you make certain modifications, or if you change the DB parameter group associated with the DB instance, you must reboot the instance for the changes to take effect.

      Rebooting a DB instance restarts the database engine service. Rebooting a DB instance results in a momentary outage, during which the DB instance status is set to rebooting.


      This is a convenience which creates an instance of the RebootDbInstanceRequest.Builder avoiding the need to create one manually via RebootDbInstanceRequest.builder()

      Parameters:
      rebootDbInstanceRequest - A Consumer that will call methods on RebootDbInstanceRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the RebootDBInstance operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidDbInstanceStateException The specified DB instance is not in the available state.
      • DbInstanceNotFoundException DBInstanceIdentifier does not refer to an existing DB instance.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • removeFromGlobalCluster

      default CompletableFuture<RemoveFromGlobalClusterResponse> removeFromGlobalCluster(RemoveFromGlobalClusterRequest removeFromGlobalClusterRequest)

      Detaches a Neptune DB cluster from a Neptune global database. A secondary cluster becomes a normal standalone cluster with read-write capability instead of being read-only, and no longer receives data from a the primary cluster.

      Parameters:
      removeFromGlobalClusterRequest -
      Returns:
      A Java Future containing the result of the RemoveFromGlobalCluster operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • GlobalClusterNotFoundException The GlobalClusterIdentifier doesn't refer to an existing global database cluster.
      • InvalidGlobalClusterStateException The global cluster is in an invalid state and can't perform the requested operation.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • removeFromGlobalCluster

      default CompletableFuture<RemoveFromGlobalClusterResponse> removeFromGlobalCluster(Consumer<RemoveFromGlobalClusterRequest.Builder> removeFromGlobalClusterRequest)

      Detaches a Neptune DB cluster from a Neptune global database. A secondary cluster becomes a normal standalone cluster with read-write capability instead of being read-only, and no longer receives data from a the primary cluster.


      This is a convenience which creates an instance of the RemoveFromGlobalClusterRequest.Builder avoiding the need to create one manually via RemoveFromGlobalClusterRequest.builder()

      Parameters:
      removeFromGlobalClusterRequest - A Consumer that will call methods on RemoveFromGlobalClusterRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the RemoveFromGlobalCluster operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • GlobalClusterNotFoundException The GlobalClusterIdentifier doesn't refer to an existing global database cluster.
      • InvalidGlobalClusterStateException The global cluster is in an invalid state and can't perform the requested operation.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • removeRoleFromDBCluster

      default CompletableFuture<RemoveRoleFromDbClusterResponse> removeRoleFromDBCluster(RemoveRoleFromDbClusterRequest removeRoleFromDbClusterRequest)

      Disassociates an Identity and Access Management (IAM) role from a DB cluster.

      Parameters:
      removeRoleFromDbClusterRequest -
      Returns:
      A Java Future containing the result of the RemoveRoleFromDBCluster operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • DbClusterRoleNotFoundException The specified IAM role Amazon Resource Name (ARN) is not associated with the specified DB cluster.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • removeRoleFromDBCluster

      default CompletableFuture<RemoveRoleFromDbClusterResponse> removeRoleFromDBCluster(Consumer<RemoveRoleFromDbClusterRequest.Builder> removeRoleFromDbClusterRequest)

      Disassociates an Identity and Access Management (IAM) role from a DB cluster.


      This is a convenience which creates an instance of the RemoveRoleFromDbClusterRequest.Builder avoiding the need to create one manually via RemoveRoleFromDbClusterRequest.builder()

      Parameters:
      removeRoleFromDbClusterRequest - A Consumer that will call methods on RemoveRoleFromDbClusterRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the RemoveRoleFromDBCluster operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • DbClusterRoleNotFoundException The specified IAM role Amazon Resource Name (ARN) is not associated with the specified DB cluster.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • removeSourceIdentifierFromSubscription

      default CompletableFuture<RemoveSourceIdentifierFromSubscriptionResponse> removeSourceIdentifierFromSubscription(RemoveSourceIdentifierFromSubscriptionRequest removeSourceIdentifierFromSubscriptionRequest)

      Removes a source identifier from an existing event notification subscription.

      Parameters:
      removeSourceIdentifierFromSubscriptionRequest -
      Returns:
      A Java Future containing the result of the RemoveSourceIdentifierFromSubscription operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SubscriptionNotFoundException The designated subscription could not be found.
      • SourceNotFoundException The source could not be found.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • removeSourceIdentifierFromSubscription

      default CompletableFuture<RemoveSourceIdentifierFromSubscriptionResponse> removeSourceIdentifierFromSubscription(Consumer<RemoveSourceIdentifierFromSubscriptionRequest.Builder> removeSourceIdentifierFromSubscriptionRequest)

      Removes a source identifier from an existing event notification subscription.


      This is a convenience which creates an instance of the RemoveSourceIdentifierFromSubscriptionRequest.Builder avoiding the need to create one manually via RemoveSourceIdentifierFromSubscriptionRequest.builder()

      Parameters:
      removeSourceIdentifierFromSubscriptionRequest - A Consumer that will call methods on RemoveSourceIdentifierFromSubscriptionRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the RemoveSourceIdentifierFromSubscription operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • SubscriptionNotFoundException The designated subscription could not be found.
      • SourceNotFoundException The source could not be found.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • removeTagsFromResource

      default CompletableFuture<RemoveTagsFromResourceResponse> removeTagsFromResource(RemoveTagsFromResourceRequest removeTagsFromResourceRequest)

      Removes metadata tags from an Amazon Neptune resource.

      Parameters:
      removeTagsFromResourceRequest -
      Returns:
      A Java Future containing the result of the RemoveTagsFromResource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbInstanceNotFoundException DBInstanceIdentifier does not refer to an existing DB instance.
      • DbSnapshotNotFoundException DBSnapshotIdentifier does not refer to an existing DB snapshot.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • removeTagsFromResource

      default CompletableFuture<RemoveTagsFromResourceResponse> removeTagsFromResource(Consumer<RemoveTagsFromResourceRequest.Builder> removeTagsFromResourceRequest)

      Removes metadata tags from an Amazon Neptune resource.


      This is a convenience which creates an instance of the RemoveTagsFromResourceRequest.Builder avoiding the need to create one manually via RemoveTagsFromResourceRequest.builder()

      Parameters:
      removeTagsFromResourceRequest - A Consumer that will call methods on RemoveTagsFromResourceRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the RemoveTagsFromResource operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbInstanceNotFoundException DBInstanceIdentifier does not refer to an existing DB instance.
      • DbSnapshotNotFoundException DBSnapshotIdentifier does not refer to an existing DB snapshot.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • resetDBClusterParameterGroup

      default CompletableFuture<ResetDbClusterParameterGroupResponse> resetDBClusterParameterGroup(ResetDbClusterParameterGroupRequest resetDbClusterParameterGroupRequest)

      Modifies the parameters of a DB cluster parameter group to the default value. To reset specific parameters submit a list of the following: ParameterName and ApplyMethod. To reset the entire DB cluster parameter group, specify the DBClusterParameterGroupName and ResetAllParameters parameters.

      When resetting the entire group, dynamic parameters are updated immediately and static parameters are set to pending-reboot to take effect on the next DB instance restart or RebootDBInstance request. You must call RebootDBInstance for every DB instance in your DB cluster that you want the updated static parameter to apply to.

      Parameters:
      resetDbClusterParameterGroupRequest -
      Returns:
      A Java Future containing the result of the ResetDBClusterParameterGroup operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidDbParameterGroupStateException The DB parameter group is in use or is in an invalid state. If you are attempting to delete the parameter group, you cannot delete it when the parameter group is in this state.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • resetDBClusterParameterGroup

      default CompletableFuture<ResetDbClusterParameterGroupResponse> resetDBClusterParameterGroup(Consumer<ResetDbClusterParameterGroupRequest.Builder> resetDbClusterParameterGroupRequest)

      Modifies the parameters of a DB cluster parameter group to the default value. To reset specific parameters submit a list of the following: ParameterName and ApplyMethod. To reset the entire DB cluster parameter group, specify the DBClusterParameterGroupName and ResetAllParameters parameters.

      When resetting the entire group, dynamic parameters are updated immediately and static parameters are set to pending-reboot to take effect on the next DB instance restart or RebootDBInstance request. You must call RebootDBInstance for every DB instance in your DB cluster that you want the updated static parameter to apply to.


      This is a convenience which creates an instance of the ResetDbClusterParameterGroupRequest.Builder avoiding the need to create one manually via ResetDbClusterParameterGroupRequest.builder()

      Parameters:
      resetDbClusterParameterGroupRequest - A Consumer that will call methods on ResetDbClusterParameterGroupRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ResetDBClusterParameterGroup operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidDbParameterGroupStateException The DB parameter group is in use or is in an invalid state. If you are attempting to delete the parameter group, you cannot delete it when the parameter group is in this state.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • resetDBParameterGroup

      default CompletableFuture<ResetDbParameterGroupResponse> resetDBParameterGroup(ResetDbParameterGroupRequest resetDbParameterGroupRequest)

      Modifies the parameters of a DB parameter group to the engine/system default value. To reset specific parameters, provide a list of the following: ParameterName and ApplyMethod. To reset the entire DB parameter group, specify the DBParameterGroup name and ResetAllParameters parameters. When resetting the entire group, dynamic parameters are updated immediately and static parameters are set to pending-reboot to take effect on the next DB instance restart or RebootDBInstance request.

      Parameters:
      resetDbParameterGroupRequest -
      Returns:
      A Java Future containing the result of the ResetDBParameterGroup operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidDbParameterGroupStateException The DB parameter group is in use or is in an invalid state. If you are attempting to delete the parameter group, you cannot delete it when the parameter group is in this state.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • resetDBParameterGroup

      default CompletableFuture<ResetDbParameterGroupResponse> resetDBParameterGroup(Consumer<ResetDbParameterGroupRequest.Builder> resetDbParameterGroupRequest)

      Modifies the parameters of a DB parameter group to the engine/system default value. To reset specific parameters, provide a list of the following: ParameterName and ApplyMethod. To reset the entire DB parameter group, specify the DBParameterGroup name and ResetAllParameters parameters. When resetting the entire group, dynamic parameters are updated immediately and static parameters are set to pending-reboot to take effect on the next DB instance restart or RebootDBInstance request.


      This is a convenience which creates an instance of the ResetDbParameterGroupRequest.Builder avoiding the need to create one manually via ResetDbParameterGroupRequest.builder()

      Parameters:
      resetDbParameterGroupRequest - A Consumer that will call methods on ResetDbParameterGroupRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the ResetDBParameterGroup operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • InvalidDbParameterGroupStateException The DB parameter group is in use or is in an invalid state. If you are attempting to delete the parameter group, you cannot delete it when the parameter group is in this state.
      • DbParameterGroupNotFoundException DBParameterGroupName does not refer to an existing DB parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • restoreDBClusterFromSnapshot

      default CompletableFuture<RestoreDbClusterFromSnapshotResponse> restoreDBClusterFromSnapshot(RestoreDbClusterFromSnapshotRequest restoreDbClusterFromSnapshotRequest)

      Creates a new DB cluster from a DB snapshot or DB cluster snapshot.

      If a DB snapshot is specified, the target DB cluster is created from the source DB snapshot with a default configuration and default security group.

      If a DB cluster snapshot is specified, the target DB cluster is created from the source DB cluster restore point with the same configuration as the original source DB cluster, except that the new DB cluster is created with the default security group.

      Parameters:
      restoreDbClusterFromSnapshotRequest -
      Returns:
      A Java Future containing the result of the RestoreDBClusterFromSnapshot operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterAlreadyExistsException User already has a DB cluster with the given identifier.
      • DbClusterQuotaExceededException User attempted to create a new DB cluster and the user has already reached the maximum allowed DB cluster quota.
      • StorageQuotaExceededException Request would result in user exceeding the allowed amount of storage available across all DB instances.
      • DbSubnetGroupNotFoundException DBSubnetGroupName does not refer to an existing DB subnet group.
      • DbSnapshotNotFoundException DBSnapshotIdentifier does not refer to an existing DB snapshot.
      • DbClusterSnapshotNotFoundException DBClusterSnapshotIdentifier does not refer to an existing DB cluster snapshot.
      • InsufficientDbClusterCapacityException The DB cluster does not have enough capacity for the current operation.
      • InsufficientStorageClusterCapacityException There is insufficient storage available for the current action. You may be able to resolve this error by updating your subnet group to use different Availability Zones that have more storage available.
      • InvalidDbSnapshotStateException The state of the DB snapshot does not allow deletion.
      • InvalidDbClusterSnapshotStateException The supplied value is not a valid DB cluster snapshot state.
      • StorageQuotaExceededException Request would result in user exceeding the allowed amount of storage available across all DB instances.
      • InvalidVpcNetworkStateException DB subnet group does not cover all Availability Zones after it is created because users' change.
      • InvalidRestoreException Cannot restore from vpc backup to non-vpc DB instance.
      • DbSubnetGroupNotFoundException DBSubnetGroupName does not refer to an existing DB subnet group.
      • InvalidSubnetException The requested subnet is invalid, or multiple subnets were requested that are not all in a common VPC.
      • OptionGroupNotFoundException The designated option group could not be found.
      • KmsKeyNotAccessibleException Error accessing KMS key.
      • DbClusterParameterGroupNotFoundException DBClusterParameterGroupName does not refer to an existing DB Cluster parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • restoreDBClusterFromSnapshot

      default CompletableFuture<RestoreDbClusterFromSnapshotResponse> restoreDBClusterFromSnapshot(Consumer<RestoreDbClusterFromSnapshotRequest.Builder> restoreDbClusterFromSnapshotRequest)

      Creates a new DB cluster from a DB snapshot or DB cluster snapshot.

      If a DB snapshot is specified, the target DB cluster is created from the source DB snapshot with a default configuration and default security group.

      If a DB cluster snapshot is specified, the target DB cluster is created from the source DB cluster restore point with the same configuration as the original source DB cluster, except that the new DB cluster is created with the default security group.


      This is a convenience which creates an instance of the RestoreDbClusterFromSnapshotRequest.Builder avoiding the need to create one manually via RestoreDbClusterFromSnapshotRequest.builder()

      Parameters:
      restoreDbClusterFromSnapshotRequest - A Consumer that will call methods on RestoreDbClusterFromSnapshotRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the RestoreDBClusterFromSnapshot operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterAlreadyExistsException User already has a DB cluster with the given identifier.
      • DbClusterQuotaExceededException User attempted to create a new DB cluster and the user has already reached the maximum allowed DB cluster quota.
      • StorageQuotaExceededException Request would result in user exceeding the allowed amount of storage available across all DB instances.
      • DbSubnetGroupNotFoundException DBSubnetGroupName does not refer to an existing DB subnet group.
      • DbSnapshotNotFoundException DBSnapshotIdentifier does not refer to an existing DB snapshot.
      • DbClusterSnapshotNotFoundException DBClusterSnapshotIdentifier does not refer to an existing DB cluster snapshot.
      • InsufficientDbClusterCapacityException The DB cluster does not have enough capacity for the current operation.
      • InsufficientStorageClusterCapacityException There is insufficient storage available for the current action. You may be able to resolve this error by updating your subnet group to use different Availability Zones that have more storage available.
      • InvalidDbSnapshotStateException The state of the DB snapshot does not allow deletion.
      • InvalidDbClusterSnapshotStateException The supplied value is not a valid DB cluster snapshot state.
      • StorageQuotaExceededException Request would result in user exceeding the allowed amount of storage available across all DB instances.
      • InvalidVpcNetworkStateException DB subnet group does not cover all Availability Zones after it is created because users' change.
      • InvalidRestoreException Cannot restore from vpc backup to non-vpc DB instance.
      • DbSubnetGroupNotFoundException DBSubnetGroupName does not refer to an existing DB subnet group.
      • InvalidSubnetException The requested subnet is invalid, or multiple subnets were requested that are not all in a common VPC.
      • OptionGroupNotFoundException The designated option group could not be found.
      • KmsKeyNotAccessibleException Error accessing KMS key.
      • DbClusterParameterGroupNotFoundException DBClusterParameterGroupName does not refer to an existing DB Cluster parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • restoreDBClusterToPointInTime

      default CompletableFuture<RestoreDbClusterToPointInTimeResponse> restoreDBClusterToPointInTime(RestoreDbClusterToPointInTimeRequest restoreDbClusterToPointInTimeRequest)

      Restores a DB cluster to an arbitrary point in time. Users can restore to any point in time before LatestRestorableTime for up to BackupRetentionPeriod days. The target DB cluster is created from the source DB cluster with the same configuration as the original DB cluster, except that the new DB cluster is created with the default DB security group.

      This action only restores the DB cluster, not the DB instances for that DB cluster. You must invoke the CreateDBInstance action to create DB instances for the restored DB cluster, specifying the identifier of the restored DB cluster in DBClusterIdentifier. You can create DB instances only after the RestoreDBClusterToPointInTime action has completed and the DB cluster is available.

      Parameters:
      restoreDbClusterToPointInTimeRequest -
      Returns:
      A Java Future containing the result of the RestoreDBClusterToPointInTime operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterAlreadyExistsException User already has a DB cluster with the given identifier.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • DbClusterQuotaExceededException User attempted to create a new DB cluster and the user has already reached the maximum allowed DB cluster quota.
      • DbClusterSnapshotNotFoundException DBClusterSnapshotIdentifier does not refer to an existing DB cluster snapshot.
      • DbSubnetGroupNotFoundException DBSubnetGroupName does not refer to an existing DB subnet group.
      • InsufficientDbClusterCapacityException The DB cluster does not have enough capacity for the current operation.
      • InsufficientStorageClusterCapacityException There is insufficient storage available for the current action. You may be able to resolve this error by updating your subnet group to use different Availability Zones that have more storage available.
      • InvalidDbClusterSnapshotStateException The supplied value is not a valid DB cluster snapshot state.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • InvalidDbSnapshotStateException The state of the DB snapshot does not allow deletion.
      • InvalidRestoreException Cannot restore from vpc backup to non-vpc DB instance.
      • InvalidSubnetException The requested subnet is invalid, or multiple subnets were requested that are not all in a common VPC.
      • InvalidVpcNetworkStateException DB subnet group does not cover all Availability Zones after it is created because users' change.
      • KmsKeyNotAccessibleException Error accessing KMS key.
      • OptionGroupNotFoundException The designated option group could not be found.
      • StorageQuotaExceededException Request would result in user exceeding the allowed amount of storage available across all DB instances.
      • DbClusterParameterGroupNotFoundException DBClusterParameterGroupName does not refer to an existing DB Cluster parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • restoreDBClusterToPointInTime

      default CompletableFuture<RestoreDbClusterToPointInTimeResponse> restoreDBClusterToPointInTime(Consumer<RestoreDbClusterToPointInTimeRequest.Builder> restoreDbClusterToPointInTimeRequest)

      Restores a DB cluster to an arbitrary point in time. Users can restore to any point in time before LatestRestorableTime for up to BackupRetentionPeriod days. The target DB cluster is created from the source DB cluster with the same configuration as the original DB cluster, except that the new DB cluster is created with the default DB security group.

      This action only restores the DB cluster, not the DB instances for that DB cluster. You must invoke the CreateDBInstance action to create DB instances for the restored DB cluster, specifying the identifier of the restored DB cluster in DBClusterIdentifier. You can create DB instances only after the RestoreDBClusterToPointInTime action has completed and the DB cluster is available.


      This is a convenience which creates an instance of the RestoreDbClusterToPointInTimeRequest.Builder avoiding the need to create one manually via RestoreDbClusterToPointInTimeRequest.builder()

      Parameters:
      restoreDbClusterToPointInTimeRequest - A Consumer that will call methods on RestoreDbClusterToPointInTimeRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the RestoreDBClusterToPointInTime operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterAlreadyExistsException User already has a DB cluster with the given identifier.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • DbClusterQuotaExceededException User attempted to create a new DB cluster and the user has already reached the maximum allowed DB cluster quota.
      • DbClusterSnapshotNotFoundException DBClusterSnapshotIdentifier does not refer to an existing DB cluster snapshot.
      • DbSubnetGroupNotFoundException DBSubnetGroupName does not refer to an existing DB subnet group.
      • InsufficientDbClusterCapacityException The DB cluster does not have enough capacity for the current operation.
      • InsufficientStorageClusterCapacityException There is insufficient storage available for the current action. You may be able to resolve this error by updating your subnet group to use different Availability Zones that have more storage available.
      • InvalidDbClusterSnapshotStateException The supplied value is not a valid DB cluster snapshot state.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • InvalidDbSnapshotStateException The state of the DB snapshot does not allow deletion.
      • InvalidRestoreException Cannot restore from vpc backup to non-vpc DB instance.
      • InvalidSubnetException The requested subnet is invalid, or multiple subnets were requested that are not all in a common VPC.
      • InvalidVpcNetworkStateException DB subnet group does not cover all Availability Zones after it is created because users' change.
      • KmsKeyNotAccessibleException Error accessing KMS key.
      • OptionGroupNotFoundException The designated option group could not be found.
      • StorageQuotaExceededException Request would result in user exceeding the allowed amount of storage available across all DB instances.
      • DbClusterParameterGroupNotFoundException DBClusterParameterGroupName does not refer to an existing DB Cluster parameter group.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • startDBCluster

      default CompletableFuture<StartDbClusterResponse> startDBCluster(StartDbClusterRequest startDbClusterRequest)

      Starts an Amazon Neptune DB cluster that was stopped using the Amazon console, the Amazon CLI stop-db-cluster command, or the StopDBCluster API.

      Parameters:
      startDbClusterRequest -
      Returns:
      A Java Future containing the result of the StartDBCluster operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • InvalidDbInstanceStateException The specified DB instance is not in the available state.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • startDBCluster

      default CompletableFuture<StartDbClusterResponse> startDBCluster(Consumer<StartDbClusterRequest.Builder> startDbClusterRequest)

      Starts an Amazon Neptune DB cluster that was stopped using the Amazon console, the Amazon CLI stop-db-cluster command, or the StopDBCluster API.


      This is a convenience which creates an instance of the StartDbClusterRequest.Builder avoiding the need to create one manually via StartDbClusterRequest.builder()

      Parameters:
      startDbClusterRequest - A Consumer that will call methods on StartDbClusterRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the StartDBCluster operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • InvalidDbInstanceStateException The specified DB instance is not in the available state.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • stopDBCluster

      default CompletableFuture<StopDbClusterResponse> stopDBCluster(StopDbClusterRequest stopDbClusterRequest)

      Stops an Amazon Neptune DB cluster. When you stop a DB cluster, Neptune retains the DB cluster's metadata, including its endpoints and DB parameter groups.

      Neptune also retains the transaction logs so you can do a point-in-time restore if necessary.

      Parameters:
      stopDbClusterRequest -
      Returns:
      A Java Future containing the result of the StopDBCluster operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • InvalidDbInstanceStateException The specified DB instance is not in the available state.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • stopDBCluster

      default CompletableFuture<StopDbClusterResponse> stopDBCluster(Consumer<StopDbClusterRequest.Builder> stopDbClusterRequest)

      Stops an Amazon Neptune DB cluster. When you stop a DB cluster, Neptune retains the DB cluster's metadata, including its endpoints and DB parameter groups.

      Neptune also retains the transaction logs so you can do a point-in-time restore if necessary.


      This is a convenience which creates an instance of the StopDbClusterRequest.Builder avoiding the need to create one manually via StopDbClusterRequest.builder()

      Parameters:
      stopDbClusterRequest - A Consumer that will call methods on StopDbClusterRequest.Builder to create a request.
      Returns:
      A Java Future containing the result of the StopDBCluster operation returned by the service.
      The CompletableFuture returned by this method can be completed exceptionally with the following exceptions. The exception returned is wrapped with CompletionException, so you need to invoke Throwable.getCause() to retrieve the underlying exception.
      • DbClusterNotFoundException DBClusterIdentifier does not refer to an existing DB cluster.
      • InvalidDbClusterStateException The DB cluster is not in a valid state.
      • InvalidDbInstanceStateException The specified DB instance is not in the available state.
      • SdkException Base class for all exceptions that can be thrown by the SDK (both service and client). Can be used for catch all scenarios.
      • SdkClientException If any client side error occurs such as an IO related failure, failure to get credentials, etc.
      • NeptuneException Base class for all service exceptions. Unknown exceptions will be thrown as an instance of this type.
      See Also:

    • waiter

      default NeptuneAsyncWaiter waiter()
      Create an instance of NeptuneAsyncWaiter using this client.

      Waiters created via this method are managed by the SDK and resources will be released when the service client is closed.

      Returns:
      an instance of NeptuneAsyncWaiter

    • serviceClientConfiguration

      default NeptuneServiceClientConfiguration serviceClientConfiguration()
      Description copied from interface: SdkClient
      The SDK service client configuration exposes client settings to the user, e.g., ClientOverrideConfiguration
      Specified by:
      serviceClientConfiguration in interface AwsClient
      Specified by:
      serviceClientConfiguration in interface SdkClient
      Returns:
      SdkServiceClientConfiguration

    • create

      static NeptuneAsyncClient create()
      Create a NeptuneAsyncClient with the region loaded from the DefaultAwsRegionProviderChain and credentials loaded from the DefaultCredentialsProvider.

    • builder

      static NeptuneAsyncClientBuilder builder()
      Create a builder that can be used to configure and create a NeptuneAsyncClient.