IBM Cloudant Java SDK is a client library that interacts with the IBM Cloudant APIs.
Disclaimer: This library is still a 0.x release. We do consider this library production-ready and capable, but there are still some limitations we’re working to resolve, and refinements we want to deliver. We are working really hard to minimise the disruption from now until the 1.0 release, but there may still be some changes that impact applications using this SDK. For now, be sure to pin versions to avoid surprises.
Table of Contents
- Overview
- Features
- Prerequisites
- Installation
- Using the SDK
- Questions
- Issues
- Versioning and LTS support
- Open source at IBM
- Contributing
- License
The IBM Cloudant Java SDK allows developers to programmatically
interact with IBM Cloudant
with the help of the com.ibm.cloud.cloudant package.
The purpose of this Java SDK is to wrap most of the HTTP request APIs provided by Cloudant and supply other functions to ease the usage of Cloudant. This SDK should make life easier for programmers to do what’s really important to them: developing software.
Reasons why you should consider using Cloudant Java SDK in your project:
- Supported by IBM Cloudant.
- Server compatibility with:
- IBM Cloudant.
- Apache CouchDB 3.x for data operations.
- Includes all the most popular and latest supported endpoints for applications.
- Handles the authentication.
- Familiar user experience with IBM Cloud SDKs.
- Flexibility to use either built-in models or byte-based requests and responses for documents.
- Built-in Changes feed follower (beta)
- HTTP2 support for higher performance connections to IBM Cloudant.
- Perform requests either synchronously or asynchronously.
- Instances of the client are unconditionally thread-safe.
- Transparently compresses request and response bodies.
The current version of this SDK is: 0.9.3
The project artifacts are published on the Maven Central. This is the default public repository used by Maven when searching for dependencies.
To use Maven Central within your Gradle build add mavenCentral() to the repositories in your build.gradle file:
repositories {
// other repositories...
mavenCentral()
}To use the Cloudant Java SDK, define a dependency that contains the artifact coordinates (group id, artifact id and version) for the service, like this:
Extend Maven dependencies in your pom.xml file with the cloudant library.
<dependencies>
<!--> other dependencies... </-->
<dependency>
<groupId>com.ibm.cloud</groupId>
<artifactId>cloudant</artifactId>
<version>0.9.3</version>
</dependency>
</dependencies>Add the cloudant library to the dependencies in your build.gradle file:
dependencies {
// other dependencies...
implementation group: "com.ibm.cloud", name: "cloudant", version: "0.9.3"
}For fundamental SDK usage information and config options, please see the common IBM Cloud SDK documentation.
This library requires configuration with a service URL and Cloudant service credentials to authenticate with your account.
There are several ways to set these authentication properties:
- As environment variables
- The programmatic approach
- With an external credentials file
The following section describes the different authentication types and provides environment variable examples. Examples for other configuration methods are available by following the provided links.
This library requires credentials to authenticate with IBM Cloudant. These credentials may be:
- IBM Cloud IAM credentials (can be used with authentication types
CONTAINER,VPCandIAM)- IBM Cloud account user, service ID or trusted profile credentials that have been granted access to the IBM Cloud Cloudant resource instance.
- IBM Cloudant service credentials generated by the IBM Cloud Cloudant resource instance.
- Username and password credentials (can be used with authentication types
COUCHDB_SESSIONandBASIC)- IBM Cloudant service credentials generated for an IBM Cloud Cloudant resource instance not configured as
IAM only. - IBM Cloudant legacy credentials (i.e. username and password) for instances not in IBM Cloud.
- IBM Cloudant legacy API keys.
- IBM Cloudant service credentials generated for an IBM Cloud Cloudant resource instance not configured as
For other compatible APIs that are not Cloudant accounts (e.g. Apache CouchDB) non-IAM based authentication types must be used.
This table summarizes the available authentication types. The authentication types are listed in order of recommendation, preferably use the authentication type from the first row in the table that is compatible with your environment.
| Authentication type | Recommended for | AUTH_TYPE |
Description |
|---|---|---|---|
| IAM Trusted Profiles compute resource (container) | Cloudant (SDK running in IBM Cloud IKS) |
CONTAINER |
Obtains a compute resource (CR) token from the container. Exchanges the CR token for an IAM access_token.Adds an Authorization: Bearer <access_token> header to each HTTP request.Automatically renews the access token when needed. |
| IAM Trusted Profiles compute resource (VPC) | Cloudant (SDK running in IBM Cloud VPC) |
VPC |
Obtains an identity token from the VPC instance metadata. Exchanges the identity token for an IAM access_token.Adds an Authorization: Bearer <access_token> header to each HTTP request.Automatically renews the access token when needed. |
| IAM API key | Cloudant | IAM |
Exchanges an IAM API key for an IAM access_token.Adds an Authorization: Bearer <access_token> header to each HTTP request.Automatically renews the access token when needed. |
| Session cookie | Cloudant (legacy credentials & instances without IAM) Apache CouchDB |
COUCHDB_SESSION |
Exchanges credentials with /_session endpoint to retrieve a cookie.Adds Cookie header and content to each HTTP request.Automatically renews session when needed. |
| Bearer token | Apache CouchDB (using JWT authentication) |
BEARERTOKEN |
Adds an Authorization: Bearer <token> to each HTTP request.No token management or renewal. Also compatible with IAM access tokens managed independently of the SDK. |
| Basic | Apache CouchDB (if cookies are not enabled) |
BASIC |
Adds an Authorization: Basic <encoded username and password> header to each HTTP request. |
| None | - | NOAUTH |
Note that this authentication type only works for operations against a database allowing access for unauthenticated users. |
The default authentication type for the SDK is CONTAINER unless APIKEY configuration is supplied, which changes the default authentication type to IAM.
The default service name is CLOUDANT so CLOUDANT_ prefixed names are used in these examples.
Any custom service name prefix can be used as long as the matching name is used to instantiate the SDK client and the same prefix is used for all configuration options.
For Cloudant IAM API key authentication, set the following environmental variables by
replacing the <url> and <apikey> with your proper
service credentials. There is no need to set
CLOUDANT_AUTH_TYPE to IAM because it is the default when an APIKEY is set.
CLOUDANT_URL=<url>
CLOUDANT_APIKEY=<apikey>For Cloudant IAM Trusted profile compute resource container authentication, set the following environmental variables by
replacing the <url> and <id> with your values. There is no need to set
CLOUDANT_AUTH_TYPE to CONTAINER because it is the default.
CLOUDANT_URL=<url>
CLOUDANT_IAM_PROFILE_ID=<id>Alternatively a profile name may be used instead of an ID by replacing CLOUDANT_IAM_PROFILE_ID with CLOUDANT_IAM_PROFILE_NAME.
For Cloudant IAM Trusted profile compute resource vpc authentication, set the following environmental variables by
replacing the <url> and <id> with your values.
CLOUDANT_AUTH_TYPE=VPC
CLOUDANT_URL=<url>
CLOUDANT_IAM_PROFILE_ID=<id>Alternatively a profile CRN may be used instead of an ID by replacing CLOUDANT_IAM_PROFILE_ID with CLOUDANT_IAM_PROFILE_CRN.
For COUCHDB_SESSION authentication, set the following environmental variables
by replacing the <url>, <username> and <password> with your proper
service credentials.
CLOUDANT_AUTH_TYPE=COUCHDB_SESSION
CLOUDANT_URL=<url>
CLOUDANT_USERNAME=<username>
CLOUDANT_PASSWORD=<password>To use an external configuration file, the Cloudant API docs, or the general SDK usage information will guide you.
To learn more about how to use programmatic authentication, see the related documentation in the Cloudant API docs or in the Java SDK Core document about authentication.
The SDK supports a generalized retry feature that can automatically retry on common errors.
The automatic retries section has details on how to enable the retries with default values and customize the retries programmatically or with external configuration.
No request timeout is defined, but a 60s connect, a 2.5m read and a 60s write timeout are set by default. Be sure to set a request timeout appropriate to your application usage and environment. The request timeout section contains details on how to change the value.
Note: System settings may take precedence over configured timeout values.
The following code examples authenticate with the environment variables.
Note: This example code assumes that orders database does not exist in your account.
This example code creates orders database and adds a new document "example"
into it. To connect, you must set your environment variables with
the service url, authentication type and authentication credentials
of your Cloudant service.
Cloudant environment variable naming starts with a service name prefix that identifies your service.
By default, this is CLOUDANT, see the settings in the
authentication with environment variables section.
If you would like to rename your Cloudant service from CLOUDANT,
you must use your defined service name as the prefix for all Cloudant related environment variables.
Once the environment variables are set, you can try out the code examples.
import com.ibm.cloud.cloudant.v1.Cloudant;
import com.ibm.cloud.cloudant.v1.model.Document;
import com.ibm.cloud.cloudant.v1.model.DocumentResult;
import com.ibm.cloud.cloudant.v1.model.Ok;
import com.ibm.cloud.cloudant.v1.model.PostDocumentOptions;
import com.ibm.cloud.cloudant.v1.model.PutDatabaseOptions;
// Uncomment import below if using "putDocument" method
// import com.ibm.cloud.cloudant.v1.model.PutDocumentOptions;
import com.ibm.cloud.sdk.core.service.exception.ServiceResponseException;
public class CreateDbAndDoc {
public static void main(String[] args) {
// 1. Create a client with `CLOUDANT` default service name ============
Cloudant client = Cloudant.newInstance();
// 2. Create a database ===============================================
// Create a database object with "orders" id
String exampleDbName = "orders";
PutDatabaseOptions putDbOptions =
new PutDatabaseOptions.Builder().db(exampleDbName).build();
// Try to create database if it doesn't exist
try {
Ok putDatabaseResult = client
.putDatabase(putDbOptions)
.execute()
.getResult();
if (putDatabaseResult.isOk()) {
System.out.println("\"" + exampleDbName +
"\" database created.");
}
} catch (ServiceResponseException sre) {
if (sre.getStatusCode() == 412)
System.out.println("Cannot create \"" + exampleDbName +
"\" database, it already exists.");
}
// 3. Create a document ===============================================
// Create a document object with "example" id
String exampleDocId = "example";
Document exampleDocument = new Document();
// Setting id for the document is optional when "postDocument" method is used for CREATE.
// When id is not provided the server will generate one for your document.
exampleDocument.setId(exampleDocId);
// Add "name" and "joined" fields to the document
exampleDocument.put("name", "Bob Smith");
exampleDocument.put("joined", "2019-01-24T10:42:59.000Z");
// Save the document in the database with "postDocument" method
PostDocumentOptions createDocumentOptions =
new PostDocumentOptions.Builder()
.db(exampleDbName)
.document(exampleDocument)
.build();
DocumentResult createDocumentResponse = client
.postDocument(createDocumentOptions)
.execute()
.getResult();
// ====================================================================
// Note: saving the document can also be done with the "putDocument"
// method. In this case `docId` is required for a CREATE operation:
/*
PutDocumentOptions createDocumentOptions =
new PutDocumentOptions.Builder()
.db(exampleDbName)
.docId(exampleDocId)
.document(exampleDocument)
.build();
DocumentResult createDocumentResponse = client
.putDocument(createDocumentOptions)
.execute()
.getResult();
*/
// ====================================================================
// Keeping track of the revision number of the document object
// is necessary for further UPDATE/DELETE operations:
exampleDocument.setRev(createDocumentResponse.getRev());
System.out.println("You have created the document:\n" +
exampleDocument);
}
}When you run the code, you see a result similar to the following output.
"orders" database created.
You have created the document:
{
"_id": "example",
"_rev": "1-1b403633540686aa32d013fda9041a5d",
"joined": "2019-01-24T10:42:99.000Z",
"name": "Bob Smith"
}
Note: This example code assumes that you have created both the orders
database and the example document by
running the previous example code
successfully. Otherwise, the following error message occurs, "Cannot delete document because either 'orders'
database or 'example' document was not found."
Gather database information example
import com.ibm.cloud.cloudant.v1.Cloudant;
import com.ibm.cloud.cloudant.v1.model.DatabaseInformation;
import com.ibm.cloud.cloudant.v1.model.Document;
import com.ibm.cloud.cloudant.v1.model.GetDatabaseInformationOptions;
import com.ibm.cloud.cloudant.v1.model.GetDocumentOptions;
import com.ibm.cloud.cloudant.v1.model.ServerInformation;
public class GetInfoFromExistingDatabase {
public static void main(String[] args) {
// 1. Create a client with `CLOUDANT` default service name ============
Cloudant client = Cloudant.newInstance();
// 2. Get server information ==========================================
ServerInformation serverInformation = client
.getServerInformation()
.execute()
.getResult();
System.out.println("Server Version: " +
serverInformation.getVersion());
// 3. Get database information for "orders" =========================
String dbName = "orders";
GetDatabaseInformationOptions dbInformationOptions =
new GetDatabaseInformationOptions.Builder(dbName).build();
DatabaseInformation dbInformationResponse = client
.getDatabaseInformation(dbInformationOptions)
.execute()
.getResult();
// 4. Show document count in database =================================
Long documentCount = dbInformationResponse.getDocCount();
System.out.println("Document count in \"" +
dbInformationResponse.getDbName() +
"\" database is " + documentCount +
".");
// 5. Get "example" document out of the database by document id ===========
GetDocumentOptions getDocOptions = new GetDocumentOptions.Builder()
.db(dbName)
.docId("example")
.build();
Document documentExample = client
.getDocument(getDocOptions)
.execute()
.getResult();
System.out.println("Document retrieved from database:\n" +
documentExample);
}
}Server Version: 2.1.1
Document count in "orders" database is 1.
Document retrieved from database:
{
"_id": "example",
"_rev": "1-1b403633540686aa32d013fda9041a5d",
"name": "Bob Smith",
"joined": "2019-01-24T10:42:99.000Z"
}
Note: This example code assumes that you have created both the orders
database and the example document by
running the previous example code
successfully. Otherwise, the following error message occurs, "Cannot update document because either 'orders'
database or 'example' document was not found."
Update code example
import com.ibm.cloud.cloudant.v1.Cloudant;
import com.ibm.cloud.cloudant.v1.model.Document;
import com.ibm.cloud.cloudant.v1.model.DocumentResult;
import com.ibm.cloud.cloudant.v1.model.GetDocumentOptions;
import com.ibm.cloud.cloudant.v1.model.PostDocumentOptions;
// Uncomment import below if using "putDocument" method
// import com.ibm.cloud.cloudant.v1.model.PutDocumentOptions;
import com.ibm.cloud.sdk.core.service.exception.NotFoundException;
// Uncomment import below if using response byte stream
// import java.io.InputStream;
public class UpdateDoc {
public static void main(String[] args) {
// 1. Create a client with `CLOUDANT` default service name ============
Cloudant client = Cloudant.newInstance();
// 2. Update the document =============================================
// Set the options to get the document out of the database if it exists
String exampleDbName = "orders";
GetDocumentOptions documentInfoOptions =
new GetDocumentOptions.Builder()
.db(exampleDbName)
.docId("example")
.build();
try {
// Try to get the document if it previously existed in the database
Document document = client
.getDocument(documentInfoOptions)
.execute()
.getResult();
// Note: for response byte stream use:
/*
InputStream documentAsByteStream =
client.getDocumentAsStream(documentInfoOptions)
.execute()
.getResult();
*/
// Add Bob Smith's address to the document
document.put("address", "19 Front Street, Darlington, DL5 1TY");
// Remove the joined property from document object
document.removeProperty("joined");
// Update the document in the database
PostDocumentOptions updateDocumentOptions =
new PostDocumentOptions.Builder()
.db(exampleDbName)
.document(document)
.build();
// ================================================================
// Note: for request byte stream use:
/*
PostDocumentOptions updateDocumentOptions =
new PostDocumentOptions.Builder()
.db(exampleDbName)
.contentType("application/json")
.body(documentAsByteStream)
.build();
*/
// ================================================================
DocumentResult updateDocumentResponse = client
.postDocument(updateDocumentOptions)
.execute()
.getResult();
// ====================================================================
// Note: updating the document can also be done with the "putDocument"
// method. docId and rev are required for an UPDATE operation,
// but rev can be provided in the document object too:
/*
PutDocumentOptions updateDocumentOptions =
new PutDocumentOptions.Builder()
.db(exampleDbName)
.docId(document.getId()) // docId is a required parameter
.rev(document.getRev())
.document(document) // rev in the document object CAN replace above `rev` parameter
.build();
DocumentResult updateDocumentResponse = client
.putDocument(updateDocumentOptions)
.execute()
.getResult();
*/
// ====================================================================
// Keeping track of the latest revision number of the document object
// is necessary for further UPDATE/DELETE operations:
document.setRev(updateDocumentResponse.getRev());
System.out.println("You have updated the document:\n" + document);
} catch (NotFoundException nfe) {
System.out.println("Cannot update document because " +
"either \"orders\" database or the \"example\" " +
"document was not found.");
}
}
}You have updated the document:
{
"_id": "example",
"_rev": "2-4e2178e85cffb32d38ba4e451f6ca376",
"address": "19 Front Street, Darlington, DL5 1TY",
"name": "Bob Smith"
}
Note: This example code assumes that you have created both the orders
database and the example document by
running the previous example code
successfully. Otherwise, the following error message occurs, "Cannot delete document because either 'orders'
database or 'example' document was not found."
Delete code example
import com.ibm.cloud.cloudant.v1.Cloudant;
import com.ibm.cloud.cloudant.v1.model.DeleteDocumentOptions;
import com.ibm.cloud.cloudant.v1.model.Document;
import com.ibm.cloud.cloudant.v1.model.DocumentResult;
import com.ibm.cloud.cloudant.v1.model.GetDocumentOptions;
import com.ibm.cloud.sdk.core.service.exception.NotFoundException;
public class DeleteDoc {
public static void main(String[] args) {
// 1. Create a client with `CLOUDANT` default service name ============
Cloudant client = Cloudant.newInstance();
// 2. Delete the document =============================================
// Set the options to get the document out of the database if it exists
String exampleDbName = "orders";
String exampleDocId = "example";
GetDocumentOptions documentInfoOptions =
new GetDocumentOptions.Builder()
.db(exampleDbName)
.docId(exampleDocId)
.build();
try {
// Try to get the document if it previously existed in the database
Document document = client
.getDocument(documentInfoOptions)
.execute()
.getResult();
// Delete the document from the database
DeleteDocumentOptions deleteDocumentOptions =
new DeleteDocumentOptions.Builder()
.db(exampleDbName)
.docId(exampleDocId) // docId is required for DELETE
.rev(document.getRev()) // rev is required for DELETE
.build();
DocumentResult deleteDocumentResponse = client
.deleteDocument(deleteDocumentOptions)
.execute()
.getResult();
if (deleteDocumentResponse.isOk()) {
System.out.println("You have deleted the document.");
}
} catch (NotFoundException nfe) {
System.out.println("Cannot delete document because " +
"either \"orders\" database or the \"example\" " +
"document was not found.");
}
}
}You have deleted the document.
For a complete list of code examples, see the examples directory.
For sample code on handling errors, see Cloudant API docs.
For endpoints that read or write document content it is possible to bypass usage of the built-in object with byte streams.
Depending on the specific SDK operation it may be possible to:
- accept a user-provided byte stream to send to the server as a request body
- return a byte stream of the server response body to the user
Request byte stream can be supplied for builder objects that have the body method.
For these cases you can pass this byte stream directly to the HTTP request body.
Response byte stream is supported in functions with the suffix of AsStream.
The returned byte stream allows the response body to be consumed
without triggering JSON unmarshalling that is typically performed by the SDK.
The update document section contains examples for both request and response byte stream cases.
The API reference contains further examples of using byte streams. They are titled "Example request as stream" and are initially collapsed. Expand them to see examples of:
-
Byte requests:
-
Byte responses:
- Cloudant API docs: API reference including usage examples for Cloudant Java SDK API.
- Javadoc: Cloudant Java SDK API Documentation.
- Cloudant docs: The official documentation page for Cloudant.
- Cloudant blog: Many useful articles about how to optimize Cloudant for common problems.
The SDK provides a changes feed follower utility (currently beta).
This helper utility connects to the _changes endpoint and returns the individual change items.
It removes some of the complexity of using the _changes endpoint by setting some options automatically
and providing error suppression and retries.
Tip: the changes feed often does not meet user expectations or assumptions.
Consult the Cloudant changes feed FAQ to get a better understanding of the limitations and suitable use-cases before using the changes feed in your application.
There are two modes of operation:
- Start mode
- Fetches the changes from the supplied
sincesequence (by default the feed will start fromnow). - Fetches all available changes and then continues listening for new changes indefinitely unless encountering an end condition.
- An example use case for this mode is event driven workloads.
- Fetches the changes from the supplied
- Start one-off mode
- Fetches the changes from the supplied
sincesequence (by default the feed will start from the beginning). - Fetches all available changes and then stops when either there are no further changes pending or encountering an end condition.
- An example use case for this mode is ETL style workloads.
- Fetches the changes from the supplied
The SDK's model of changes feed options is also used to configure the follower. However, a subset of the options are invalid as they are configured internally by the implementation. Supplying these options when instantiating the follower causes an error. The invalid options are:
descendingfeedheartbeatlastEventId- usesinceinsteadtimeout- Only the value of
_selectoris permitted for thefilteroption. This restriction is because selector based filters perform better than JavaScript backed filters. Configuring a non-selector based filter will cause the follower to error.
Note that the limit parameter will terminate the follower at the given number of changes in either
operating mode.
The changes follower requires the client to have HTTP timeouts of at least 1 minute and will error during instantiation if it is insufficient. The default client configuration has sufficiently long timeouts.
For use-cases where these configuration limitations are deemed too restrictive then it is recommended to
write code to use the SDK's POST _changes API instead of the follower.
By default, the changes follower will suppress transient errors indefinitely and attempt to run to completion or listen forever as dictated by the operating mode. For applications where that is not desirable an optional error tolerance duration may be specified to control the time since the last successful response that transient errors will be suppressed. This can be used, for example, by applications as a grace period before reporting an error and requiring intervention.
There are some additional points to consider for error suppression:
- Errors considered terminal, for example, the database not existing or invalid credentials are never suppressed and will error immediately.
- The error suppression duration is not guaranteed to fire immediately after lapsing and should be considered a minimum suppression time.
- The changes follower will back-off between retries and as such may remain paused for a short while after the transient errors have resolved.
- If the underlying SDK client used to initialize the follower also has retries configured then errors could be suppressed for significantly longer than the follower's configured error tolerance duration depending on the configuration options.
For both modes:
- The end conditions are:
- A terminal error (HTTP codes
400,401,403404). - Transient errors occur for longer than the error tolerance duration. Transient errors are all other HTTP status codes and connection errors.
- The number of changes received reaches the configured
limit. - The feed is terminated early by calling stop.
- A terminal error (HTTP codes
As is true for the _changes endpoint change items have at least once delivery and an individual item
may be received multiple times. When using the follower change items may be repeated even within a limited
number of changes (i.e. using the limit option) this is a minor difference from using limit on the HTTP native API.
The follower is not optimized for some use cases and it is not recommended to use it in cases where:
- Setting
include_docsand larger document sizes (for example > 10 kiB). - The volume of changes is very high (if the rate of changes in the database exceeds the follower's rate of pulling them it will never catch-up).
In these cases use-case specific control over the number of change requests made and the content size of the responses
may be achieved by using the SDK's POST _changes API.
The changes follower does not checkpoint since it has no information about whether a change item has been
processed by the consuming application after being received. It is the application developer's responsibility
to store the sequence IDs to have appropriate checkpoints and to re-initialize the follower with the required
since value after, for example, the application restarts.
The frequency and conditions for checkpointing are application specific and some applications may be tolerant of dropped changes. This section is intended only to provide general guidance on how to avoid missing changes.
To guarantee processing of all changes the sequence ID from a change item must not be persisted until after
the processing of the change item by the application has completed. As indicated previously change items are
delivered at least once so application code must be able to handle repeated changes already and it is
preferable to restart from an older since value and receive changes again than risk missing them.
The sequence IDs are available on each change item by default, but may be omitted from some change items when
using the seq_interval configuration option. Infrequent sequence IDs may improve performance by reducing
the amount of data that needs to be transferred, but the trade-off is that more changes will be repeated if
it is necessary to resume the changes follower.
Extreme care should be taken with persisting sequences if choosing to process change items in parallel as there is a considerable risk of missing changes on a restart if the sequence is recorded out of order.
import java.time.Duration;
import com.ibm.cloud.cloudant.features.ChangesFollower;
import com.ibm.cloud.cloudant.v1.Cloudant;
import com.ibm.cloud.cloudant.v1.model.PostChangesOptions;
public class Initialize {
public static void main(String[] args) {
Cloudant client = Cloudant.newInstance();
PostChangesOptions options = new PostChangesOptions.Builder("example") // Required: the database name.
.limit(100) // Optional: return only 100 changes (including duplicates).
.since("3-g1AG3...") // Optional: start from this sequence ID (e.g. with a value read from persistent storage).
.build();
ChangesFollower changesFollower = new ChangesFollower(
client, // Required: the Cloudant service client instance.
options, // Required: changes feed configuration options object.
Duration.ofSeconds(10) // Optional: suppress transient errors for at least 10 seconds before terminating.
);
}
}import java.util.stream.Stream;
import com.ibm.cloud.cloudant.features.ChangesFollower;
import com.ibm.cloud.cloudant.v1.Cloudant;
import com.ibm.cloud.cloudant.v1.model.ChangesResultItem;
import com.ibm.cloud.cloudant.v1.model.PostChangesOptions;
public class Start {
public static void main(String[] args) {
Cloudant client = Cloudant.newInstance();
PostChangesOptions options = new PostChangesOptions.Builder("example")
.build();
ChangesFollower changesFollower = new ChangesFollower(client, options);
Stream<ChangesResultItem> changesItems = changesFollower.start();
// Note: java.util.Stream will not do anything until attached to a terminal operation.
// Invoke a Stream terminal operation to commence the flow of changes.
// e.g. changesItems.collect(...)
}
}import java.util.stream.Stream;
import com.ibm.cloud.cloudant.features.ChangesFollower;
import com.ibm.cloud.cloudant.v1.Cloudant;
import com.ibm.cloud.cloudant.v1.model.ChangesResultItem;
import com.ibm.cloud.cloudant.v1.model.PostChangesOptions;
public class StartOneOff {
public static void main(String[] args) {
Cloudant client = Cloudant.newInstance();
PostChangesOptions options = new PostChangesOptions.Builder("example")
.build();
ChangesFollower changesFollower = new ChangesFollower(client, options);
Stream<ChangesResultItem> changesItems = changesFollower.startOneOff();
// Note: java.util.Stream will not do anything until attached to a terminal operation.
// Invoke a Stream terminal operation to commence the flow of changes.
// e.g. changesItems.collect(...)
}
}import java.util.stream.Stream;
import com.ibm.cloud.cloudant.features.ChangesFollower;
import com.ibm.cloud.cloudant.v1.Cloudant;
import com.ibm.cloud.cloudant.v1.model.Change;
import com.ibm.cloud.cloudant.v1.model.ChangesResultItem;
import com.ibm.cloud.cloudant.v1.model.PostChangesOptions;
public class StartAndProcess {
public static void main(String[] args) {
Cloudant client = Cloudant.newInstance();
// Start from a perviously persisted seq
// Normally this would be read by the app from persistent storage
// e.g. String previouslyPersistedSeq = yourAppPersistenceReadFunction();
String previouslyPersistedSeq = "3-g1AG3...";
PostChangesOptions options = new PostChangesOptions.Builder("example")
.since(previouslyPersistedSeq)
.build();
ChangesFollower changesFollower = new ChangesFollower(client, options);
Stream<ChangesResultItem> changesItems = changesFollower.start();
changesItems.forEach(changesItem -> {
// do something with changes
System.out.println(changesItem.getId());
for (Change change : changesItem.getChanges()) {
System.out.println(change.getRev());
}
// when change item processing is complete app can store seq
String seq = changesItem.getSeq();
// write seq to persistent storage for use as since if required to resume later
// e.g. call yourAppPersistenceWriteFunction(seq);
});
// Note: java.util.Stream terminal operations are blocking, code here will be unreachable
// until the stream is stopped or another stop condition is reached.
// For long running followers careful consideration should be made of where the terminal
// operation is invoked.
}
}import java.util.stream.Stream;
import com.ibm.cloud.cloudant.features.ChangesFollower;
import com.ibm.cloud.cloudant.v1.Cloudant;
import com.ibm.cloud.cloudant.v1.model.Change;
import com.ibm.cloud.cloudant.v1.model.ChangesResultItem;
import com.ibm.cloud.cloudant.v1.model.PostChangesOptions;
public class StartOneOffAndProcess {
public static void main(String[] args) {
Cloudant client = Cloudant.newInstance();
// Start from a perviously persisted seq
// Normally this would be read by the app from persistent storage
// e.g. String previouslyPersistedSeq = yourAppPersistenceReadFunction();
String previouslyPersistedSeq = "3-g1AG3...";
PostChangesOptions options = new PostChangesOptions.Builder("example")
.since(previouslyPersistedSeq)
.build();
ChangesFollower changesFollower = new ChangesFollower(client, options);
Stream<ChangesResultItem> changesItems = changesFollower.startOneOff();
changesItems.forEach(changesItem -> {
// do something with changes
System.out.println(changesItem.getId());
for (Change change : changesItem.getChanges()) {
System.out.println(change.getRev());
}
// when change item processing is complete app can store seq
String seq = changesItem.getSeq();
// write seq to persistent storage for use as since if required to resume later
// e.g. call yourAppPersistenceWriteFunction(seq);
});
// Note: java.util.Stream terminal operations are blocking, code here will be unreachable
// until all changes are processed (or another stop condition is reached).
}
}import java.util.stream.Stream;
import com.ibm.cloud.cloudant.features.ChangesFollower;
import com.ibm.cloud.cloudant.v1.Cloudant;
import com.ibm.cloud.cloudant.v1.model.ChangesResultItem;
import com.ibm.cloud.cloudant.v1.model.PostChangesOptions;
public class Stop {
public static void main(String[] args) {
Cloudant client = Cloudant.newInstance();
PostChangesOptions options = new PostChangesOptions.Builder("example")
.build();
ChangesFollower changesFollower = new ChangesFollower(client, options);
Stream<ChangesResultItem> changesItems = changesFollower.start();
changesItems.forEach(changesItem -> {
// Option 1: call stop after some condition.
// Note that at least one change item must be returned
// from the stream to reach to this point.
// Note additional changes may be processed before the Stream stops.
changesFollower.stop();
});
// Option 2: call stop method when you want to end the continuous loop from
// outside the Stream. For example, you've put the changes follower in a
// separate thread and need to call stop on the main thread.
// N.B. In this context the call must be made from a different thread because
// code immediately following a Stream terminal operation is unreachable until
// the Stream has stopped.
changesFollower.stop();
}
}If you are having difficulties using this SDK or have a question about the IBM Cloud services, ask a question on Stack Overflow.
If you encounter an issue with the project, you are welcome to submit a bug report.
Before you submit a bug report, search for similar issues and review the KNOWN_ISSUES file to verify that your issue hasn't been reported yet.
Please consult the security policy before opening security related issues.
This SDK follows semantic versioning with respect to the definition of user facing APIs. This means under some circumstances breaking changes may occur within a major or minor version of the SDK related to changes in supported language platforms.
The SDK is supported on the available LTS releases of the language platform. The LTS language versions are listed in the prerequisites:
Incompatible changes from new language versions are not added to the SDK until they are available in the minimum supported language version.
When language LTS versions move out of support the following will happen:
- Existing SDK releases will continue to run on obsolete language versions, but will no longer be supported.
- The minimum language version supported by the SDK will be updated to the next available LTS.
- New language features may be added in subsequent SDK releases that will cause breaking changes if the new releases of the SDK are used with older, now unsupported, language levels.
Find more open source projects on the IBM GitHub page.
For more information, see CONTRIBUTING.
This SDK is released under the Apache 2.0 license. To read the full text of the license, see LICENSE.