-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: Remove lin_read usage from Raw HTTP client guide #2823
Conversation
* Add info about preds field. * Show example of preds field in mutation. * Remove mention of lin_read that I forgot about.
Copy pasta error.
@mrjn can you review these new docs for the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 1 of 1 files at r1.
Reviewable status: all files reviewed, 2 unresolved discussions (waiting on @danielmai)
wiki/content/clients/index.md, line 406 at r1 (raw file):
2. The set of keys modified by the transaction (`keys`). This aids in transaction conflict detection.
Every mutation would send back a new set of keys. The client must merge them with the existing set. Optionally, a client can de-dup these keys while merging.
wiki/content/clients/index.md, line 409 at r1 (raw file):
3. The set of predicates modified by the transaction (`preds`). This aids in predicate move detection. This only appears in clusters with multiple Alphas.
preds should always get filled in, and should be sent.
wiki/content/clients/index.md, line 409 at r1 (raw file): Previously, manishrjain (Manish R Jain) wrote…
Done. |
wiki/content/clients/index.md, line 406 at r1 (raw file): Previously, manishrjain (Manish R Jain) wrote…
Done. |
* Remove lin_read from client docs. * Add info about preds field. * Show example of preds field in mutation.
…-io#2823) * Remove lin_read from client docs. * Add info about preds field. * Show example of preds field in mutation.
preds
field.This change is