The relative priority for requests. Note that priority is not applicable
for [BeginTransaction][google.spanner.v1.Spanner.BeginTransaction].
The priority acts as a hint to the Cloud Spanner scheduler and does not
guarantee priority or order of execution. For example:
Some parts of a write operation always execute at PRIORITY_HIGH,
regardless of the specified priority. This may cause you to see an
increase in high priority workload even when executing a low priority
request. This can also potentially cause a priority inversion where a
lower priority request will be fulfilled ahead of a higher priority
request.
If a transaction contains multiple operations with different priorities,
Cloud Spanner does not guarantee to process the higher priority
operations first. There may be other constraints to satisfy, such as
order of operations.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["\u003cp\u003eThe content outlines various versions of the \u003ccode\u003eGoogle.Cloud.Spanner.V1\u003c/code\u003e library, ranging from version 3.5.0 to the latest beta version 5.0.0-beta05.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003ePriority\u003c/code\u003e enum within \u003ccode\u003eGoogle.Cloud.Spanner.V1.RequestOptions.Types\u003c/code\u003e defines request priorities, which are High, Low, Medium, and Unspecified, with Unspecified defaulting to High priority.\u003c/p\u003e\n"],["\u003cp\u003eRequest priority serves as a hint to the Cloud Spanner scheduler, not a strict guarantee of execution order or precedence, and it is not applicable for \u003ccode\u003eBeginTransaction\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThere are potential caveats with priority handling, such as parts of write operations executing at \u003ccode\u003ePRIORITY_HIGH\u003c/code\u003e regardless of the specified priority, potentially leading to priority inversions.\u003c/p\u003e\n"],["\u003cp\u003eThe priority level of a request does not guarantee the order in which multiple operations within a single transaction will be executed, as there may be other constraints.\u003c/p\u003e\n"]]],[],null,[]]