You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be useful if the ReadTransaction would expose the TransactionOptions like a normal transaction. that would allow users to use a read transaction to read from the system key space (e.g. the management API in the future). Without that we are not able to set the transaction.Options().SetAccessSystemKeys() option to allow access to the system key space. We would like to use read transactions in our implementation, e.g. in the Kubernetes FDB operator to ensure we are only reading from the system key space for most of our operations.
The text was updated successfully, but these errors were encountered:
that would allow users to use a read transaction to read from the system key space (e.g. the management API in the future)
I think you're confusing the system key space [\xff, \xff\xff) with the special key space [\xff\xff, \xff\xff\xff). The management API in the future will be exposed through the special key space.
That said, it does make sense to have transaction options exposed in ReadTransaction and other bindings (e.g. the java bindings) do that.
@johscheuer I have a draft PR which I think resolves this issue. Let me know if this works for you. #6318
…terface (#6318)
* Run go unit tests in ctest
* Remove unnecessary cgo directives
* go: Allow access to TransactionOptions from ReadTransaction
Closes#6265
* Try go get instead of go install
My understanding is that this should download dependencies (e.g. xerrors)
* Add -d flag to match go command for building libraries
* Avoid concurrent calls to `go get`
It would be useful if the ReadTransaction would expose the TransactionOptions like a normal transaction. that would allow users to use a read transaction to read from the system key space (e.g. the management API in the future). Without that we are not able to set the
transaction.Options().SetAccessSystemKeys()
option to allow access to the system key space. We would like to use read transactions in our implementation, e.g. in the Kubernetes FDB operator to ensure we are only reading from the system key space for most of our operations.The text was updated successfully, but these errors were encountered: