Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
1
Description
Whilst we have tests for this, they test against a dataset which is over no data. When performed over dataset(s) with data we see `json: cannot unmarshal object into Go value of type uint64`
The correct format to parse is
{
"Default" :
}
where Default is the dataverse and default is the dataset name
Attachments
Issue Links
- is cloned by
-
GOCBC-986 CLONE - GetPendingMutations looking for incorrect structure in response body
-
- Closed
-
For Gerrit Dashboard: GOCBC-977 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
136388,3 | GOCBC-977: Alter signature of GetPendingMutations | master | gocb | Status: MERGED | +2 | +1 |
Charles - I've encountered something like this in the java sdk. It fails on parsing the 'long' as the parser is stuck on START_OBJECT when it should be on INTEGER. I don't know why. When the call to decodeInto is changed to use a Class (instead of a TypeReference), it succeeds, but the resulting entry is a <String,Integer> instead of a <String,Long> - but the runtime does not seem to notice or care.
Caused by: com.couchbase.client.core.deps.com.fasterxml.jackson.databind.exc.MismatchedInputException: Cannot deserialize instance of `java.lang.Long` out of START_OBJECT token
{ "myDataset" : 0 }at [Source: (byte[])"{
"Default" :
}"; line: 2, column: 15]