Get desktop application:
View/edit binary Protocol Buffers messages
Moved to new message containing from and to
Used in:
Used in:
Only one of these will be passed. If your SDK isn't planning to support doc_id_prefix we will disable those tests through caps or some other method
This was created and named before it became "a first class part of the API". Rather than break existing implementations this will remain the same, but now represents the PrefixScan ScanType
Used in:
A Scan will result in the performer sending back a stream of (in the golden path): (1) A stream.Created result with type STREAM_KV_RANGE_SCAN, followed by (2) Zero or more ScanResult results (and/or streams.Error), followed by (1) A stream.Complete result. A streams.CancelRequest from the driver should be handled per the RFC - with a range scan cancellation sent to KV on each vbucket stream.
Used in:
Not sent on to the SDK - instead specifies how the performer should handle the streaming.
Controls how all ScanResult.contentAs() calls are done by the SDK for this scan. If not specified, the performer should not do contentAs. If there is any error from result.contentAs(), each error needs to raise a streams.Error, instead of the normal ScanResult.
Used in:
Renamed in the RFC. Used to be "without_content" and will need changing in performers
Sorting is not supported for RangeScans anymore.
As usual, parent_span_id will only be sent if the performer declares support for Caps.OBSERVABILITY_1
Since this isn't going to be present in all sdks then the logic to not use it will be on the test-driver side with @ignoreWhen
Since all SDKs do not support this option the logic to not use it will be on the driver side with @ignoreWhen
Used in:
Following three fields shouldn't be present if withoutContent was set.
This field should also be empty if the test did not set ContentAs in the Scan message
Represented as the number of seconds since January 1, 1970 (e.g. what the server returns)
Not part of the SDK response - identifies what stream this is from.
Returns the value of idsOnly from the scan associated with the result
Sorting is not supported for RangeScans anymore.
Used in:
Used in:
This is now stored as a string and the user can only pass a string. Deprecating the bytes method but not removing for the same reasons as below
If exclusive is set to false then the SDK should explicitly set it to false not leave it as default
Used in:
These options are deprecated as they were removed from the RFC. I have not removed them as it breaks compilation on existing uses which will slow down this work. Please remove when you can
Since the behaviour if a term is not supplied is to use min for from and max for to then this option is to represent the user not supplying any term
Used in: