Optional. Optional constraint on the maximum number of entities to
count.
This provides a way to set an upper bound on the number of entities
to scan, limiting latency and cost.
Unspecified is interpreted as no bound.
If a zero value is provided, a count result of zero should always be
expected.
High-Level Example:
<code><code>
AGGREGATE COUNT_UP_TO(1000) OVER ( SELECT * FROM k );
</code></code>
Requires:
Optional. Optional constraint on the maximum number of entities to
count.
This provides a way to set an upper bound on the number of entities
to scan, limiting latency and cost.
Unspecified is interpreted as no bound.
If a zero value is provided, a count result of zero should always be
expected.
High-Level Example:
<code><code>
AGGREGATE COUNT_UP_TO(1000) OVER ( SELECT * FROM k );
</code></code>
Requires:
Optional. Optional constraint on the maximum number of entities to
count.
This provides a way to set an upper bound on the number of entities
to scan, limiting latency and cost.
Unspecified is interpreted as no bound.
If a zero value is provided, a count result of zero should always be
expected.
High-Level Example:
<code><code>
AGGREGATE COUNT_UP_TO(1000) OVER ( SELECT * FROM k );
</code></code>
Requires:
Optional. Optional constraint on the maximum number of entities to
count.
This provides a way to set an upper bound on the number of entities
to scan, limiting latency and cost.
Unspecified is interpreted as no bound.
If a zero value is provided, a count result of zero should always be
expected.
High-Level Example:
<code><code>
AGGREGATE COUNT_UP_TO(1000) OVER ( SELECT * FROM k );
</code></code>
Requires:
Optional. Optional constraint on the maximum number of entities to
count.
This provides a way to set an upper bound on the number of entities
to scan, limiting latency and cost.
Unspecified is interpreted as no bound.
If a zero value is provided, a count result of zero should always be
expected.
High-Level Example:
<code><code>
AGGREGATE COUNT_UP_TO(1000) OVER ( SELECT * FROM k );
</code></code>
Requires:
Optional. Optional constraint on the maximum number of entities to
count.
This provides a way to set an upper bound on the number of entities
to scan, limiting latency and cost.
Unspecified is interpreted as no bound.
If a zero value is provided, a count result of zero should always be
expected.
High-Level Example:
<code><code>
AGGREGATE COUNT_UP_TO(1000) OVER ( SELECT * FROM k );
</code></code>
Requires:
Optional. Optional constraint on the maximum number of entities to
count.
This provides a way to set an upper bound on the number of entities
to scan, limiting latency and cost.
Unspecified is interpreted as no bound.
If a zero value is provided, a count result of zero should always be
expected.
High-Level Example:
<code><code>
AGGREGATE COUNT_UP_TO(1000) OVER ( SELECT * FROM k );
</code></code>
Requires:
Optional. Optional constraint on the maximum number of entities to
count.
This provides a way to set an upper bound on the number of entities
to scan, limiting latency and cost.
Unspecified is interpreted as no bound.
If a zero value is provided, a count result of zero should always be
expected.
High-Level Example:
<code><code>
AGGREGATE COUNT_UP_TO(1000) OVER ( SELECT * FROM k );
</code></code>
Requires:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-01-28 UTC."],[],[]]
