Graham Pople comments

Results 8 comments of


                                            Graham Pople

continued support for CallbackPreferringPlatformTransactionManager for spring-data-couchbase to implement @Transactional

For further context, the Couchbase transactions API is based around the user providing their transactional logic inside a lambda, that we can retry as needed. A simple transaction could look...

Support for protoc 3.15.0

Thanks for the suggestion @KeatsPeeks. After also upgrading everything to latest, it worked great.

Transactions documentation is outdated

There is also an odd 'leveloffset' artifact here: ` We are also looking into tighter integration of the transaction library into the spring data library ecosystem. :leveloffset: -1 `

cas of document replaced in transaction changes again on completion of transaction. @Transactional method (5.0.0-M6)

> I believe the first cas is when it is saved in the transaction 'staging' area (spring-data-couchbase has access to that cas via the transaction api), and the second cas...

Add recommended GraalVM native reflect-config.json

Hi @jvican, could you possibly share that reflect-config.json? I'm hitting the following error when compiling MpscArrayQueue with Graal and it's unclear how to resolve it: ` Caused by: java.lang.RuntimeException: java.lang.NoSuchFieldException:...

Need to always pass query_context to satisfy protostellar

Small note that this is really needed for the other platform that shall not be named :) (Though it is required for Protostellar too, yes)

use query_context even for _default scope, _default collection, except if server doesn't support it

This did get discussed as one potential path for the SDKs, but was abandoned in favour of only sending query_context if the application explicitly chose a scope based API. What...

use query_context even for _default scope, _default collection, except if server doesn't support it

Yea and doesn't break against pre 7.0 too