Collection manager not parsing errors correctly

Description

There are a number of errors that I think have changed their error message response from the server and therefore the errors are not being parsed correctly.

Here's a list of the current (7.0.0-3435 internal beta) error responses:

Scope already exists:
{"errors":{"_":"Scope with name \"2d33a596-8\" already exists"}}

Collection already exists:
{"errors":{"_":"Collection with name \"b185d9f9-0\" in scope \"7df92294-3\" already exists"}}

Scope not found:
{"errors":{"_":"Unknown error {error,{scope_not_found,\"foobar\"}}"}}

Collection not found
{"errors":{"_":"Unknown error {error,{collection_not_found,\"a9e4f276-3\",\"1141f1d0-b\"}}"}}

 

There are a number of test failures related to this: http://sdk.jenkins.couchbase.com/view/Nightly/job/jvm/job/jvm-clients/job/couchbase-jvm-clients-scipted-build-pipeline/521/testReport/com.couchbase.client.java.manager.collection/CollectionManagerIntegrationTest/

 

Environment

None

Gerrit Reviews

None

Release Notes Description

None

Activity

Show:

Matt Ingenthron December 3, 2020 at 4:39 AM

: can you triage this accordingly? Thanks!

Will Broadbelt November 6, 2020 at 10:42 AM

: Yes I agree a special release would be overkill. Having the proper named exceptions as intended would be nice, but doesn't affect the overall functionality much, so the 'affects-CC-testing' label is more appropriate here. I have updated the ticket as such.

Matt Ingenthron November 5, 2020 at 6:39 PM

: we were reviewing this earlier today. The "7.0mustpass" label really means that it needs to be fixed for the Cheshire Cat beta, which is scheduled for mid-November. If we want that, then we'd need to fix it and queue up a special release of the SDK. I think that may not be what you'd intended here?

I don't think it's a blocker for 7.0beta in any functional way, but maybe I'm wrong. Maybe I'd propose we add the "affects-CC-testing" label and ask and team to queue it up for the next release? Let me know what you think .

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Labels

Story Points

Fix versions

Affects versions

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created October 27, 2020 at 4:49 PM
Updated August 31, 2024 at 11:03 AM
Resolved December 7, 2020 at 6:35 PM
Instabug