Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs(generated): known issues updates #475

Merged
merged 1 commit into from
Sep 19, 2023
Merged

docs(generated): known issues updates #475

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 13 additions & 1 deletion KNOWN_ISSUES.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,7 +99,8 @@ As such the issue will only manifest when trying to read a design document creat

#### Facet counting deserialization errors in no match cases

When obtaining a `SearchResult` with `counts` if there are no matches a deserialization error is encountered:
In Apache CouchDB versions `3.3.2` or older and Cloudant versions `8435` and older
when obtaining a `SearchResult` with `counts` if there are no matches a deserialization error is encountered:
```
java.lang.IllegalStateException: Expected BEGIN_OBJECT but was NUMBER
```
Expand Down Expand Up @@ -178,3 +179,14 @@ As such the issue will only manifest when trying to read a replication document
```

If you need to read a replication document that uses string format source or target URLs the workaround is to use the `getDocumentAsStream` [Raw IO](/#raw-io) function with the `_replicator` database name and your replication document id to custom deserialize the response.

### Queries

#### Explain response

With Apache CouchDB versions `3.3.2` or older and Cloudant versions `8442` and older
deserialization of the `_explain` response fails when the request does not
list any `fields` to project and hence the response includes `"fields": "all_fields"`.

If it is not possible to use a newer server version the workaround is to use
[Raw IO](/#raw-io) functions to custom deserialize the response.