Skip to content

Conversation

@DemetrisChr
Copy link
Contributor

@DemetrisChr DemetrisChr commented Jan 11, 2024

The error message when the bucket does not support history retention has changed in newer server versions. Replace the error message checks for feature_not_available with a bucket capability check before sending the collection create/update request.

Copy link
Member

@avsej avsej left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like all severs return different kinds of errors

@DemetrisChr DemetrisChr force-pushed the dedup-not-allowed-this-type branch from 1a93cea to 854ccf5 Compare January 12, 2024 09:42
@DemetrisChr DemetrisChr force-pushed the dedup-not-allowed-this-type branch from 854ccf5 to bc0561a Compare January 12, 2024 09:56
@DemetrisChr DemetrisChr requested a review from avsej January 12, 2024 10:02
@DemetrisChr DemetrisChr changed the title Handle 'Not allowed on this type of bucket' response in collection create/update Add check for history retention bucket capability in collection create/update Jan 12, 2024
@DemetrisChr DemetrisChr changed the title Add check for history retention bucket capability in collection create/update CXXCBC-431: Add check for history retention bucket capability in collection create/update Jan 12, 2024
@avsej avsej merged commit 157a47b into couchbase:main Jan 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants