Indicates that no specific consistency is required, this is the fastest options, but results may not include the most recent operations which have been performed.
Indicates that the results to the query should include all operations that have occurred up until the query was started. This incurs a performance penalty of waiting for the index to catch up to the most recent operations, but provides the highest level of consistency.
Indicates that the results of the query should behave according to similar semantics as NotBounded, but following the execution of the query the index should begin updating such that following queries will likely include up to date data.
Represents the various scan consistency options that are available when querying against the views service.