Scoped Transactional queries broken
Description
Environment
None
Gerrit Reviews
None
Release Notes Description
None
Activity
Show:
David Kelly May 10, 2022 at 3:00 PMEdited
Breaking this into 2 tickets: This specific issue should be going in 4.0.1, but the broader idea of making all the transaction options/config completely testable should be a 4.0.x thing, so it is somewhat easier to schedule. That is https://couchbasecloud.atlassian.net/browse/PYCBC-1327#icft=PYCBC-1327
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
David Kelly
David KellyReporter
David Kelly
David KellyLabels
Story Points
1
Sprint
None
Fix versions
Priority
Instabug
Open Instabug
PagerDuty
PagerDuty Incident
PagerDuty

PagerDuty Incident
Sentry
Linked Issues
Sentry
Linked Issues
Zendesk Support
Linked Tickets
Zendesk Support

Linked Tickets
Created May 6, 2022 at 3:13 PM
Updated May 18, 2022 at 4:09 PM
Resolved May 16, 2022 at 2:26 PM
Instabug
The
TransactionQueryOptions
missed a change in the Scope class, so now scoped transactional queries are broken. The error -couchbase.exceptions.TransactionFailed: TransactionFailed{<message=AttributeError("'Scope' object has no attribute 'bucket'")>}
is simple to fix. However, lets instead come up with a way to test the transaction options/config classes better. We cannot just make use of all options and test the effects. Better we just insure the right thing is in the underlying c++ object. One way - have a function that returns a dict of the pycbc_core option. Then we know we are setting things correctly in the option classes.