Partition results. Each partition is a split point that can be used by RunQuery as a starting or end point for the query results. The RunQuery requests must be made with the same query supplied to this PartitionQuery request. The partition cursors will be ordered according to same ordering as the results of the query supplied to PartitionQuery. For example, if a PartitionQuery request returns partition cursors A and B, running the following three queries will return the entire result set of the original query: * * query, end_at A * * query, start_at A, end_at B * * query, start_at B An empty result may indicate that the query has too few results to be partitioned, or that the query is not yet supported for partitioning.
↳ next_page_token
string
A page token that may be used to request an additional set of results, up to the number specified by partition_count in the PartitionQuery request. If blank, there are no more results.
getPartitions
Partition results.
Each partition is a split point that can be used by RunQuery as a starting
or end point for the query results. The RunQuery requests must be made with
the same query supplied to this PartitionQuery request. The partition
cursors will be ordered according to same ordering as the results of the
query supplied to PartitionQuery.
For example, if a PartitionQuery request returns partition cursors A and B,
running the following three queries will return the entire result set of
the original query:
query, end_at A
query, start_at A, end_at B
query, start_at B
An empty result may indicate that the query has too few results to be
partitioned, or that the query is not yet supported for partitioning.
Each partition is a split point that can be used by RunQuery as a starting
or end point for the query results. The RunQuery requests must be made with
the same query supplied to this PartitionQuery request. The partition
cursors will be ordered according to same ordering as the results of the
query supplied to PartitionQuery.
For example, if a PartitionQuery request returns partition cursors A and B,
running the following three queries will return the entire result set of
the original query:
query, end_at A
query, start_at A, end_at B
query, start_at B
An empty result may indicate that the query has too few results to be
partitioned, or that the query is not yet supported for partitioning.
[[["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-09-04 UTC."],[],[],null,["# Cloud Firestore V1 Client - Class PartitionQueryResponse (1.53.0)\n\nVersion latestkeyboard_arrow_down\n\n- [1.53.0 (latest)](/php/docs/reference/cloud-firestore/latest/V1.PartitionQueryResponse)\n- [1.52.0](/php/docs/reference/cloud-firestore/1.52.0/V1.PartitionQueryResponse)\n- [1.51.0](/php/docs/reference/cloud-firestore/1.51.0/V1.PartitionQueryResponse)\n- [1.50.0](/php/docs/reference/cloud-firestore/1.50.0/V1.PartitionQueryResponse)\n- [1.48.1](/php/docs/reference/cloud-firestore/1.48.1/V1.PartitionQueryResponse)\n- [1.47.3](/php/docs/reference/cloud-firestore/1.47.3/V1.PartitionQueryResponse)\n- [1.46.0](/php/docs/reference/cloud-firestore/1.46.0/V1.PartitionQueryResponse)\n- [1.45.2](/php/docs/reference/cloud-firestore/1.45.2/V1.PartitionQueryResponse)\n- [1.44.1](/php/docs/reference/cloud-firestore/1.44.1/V1.PartitionQueryResponse)\n- [1.43.3](/php/docs/reference/cloud-firestore/1.43.3/V1.PartitionQueryResponse)\n- [1.40.0](/php/docs/reference/cloud-firestore/1.40.0/V1.PartitionQueryResponse)\n- [1.39.0](/php/docs/reference/cloud-firestore/1.39.0/V1.PartitionQueryResponse)\n- [1.38.0](/php/docs/reference/cloud-firestore/1.38.0/V1.PartitionQueryResponse)\n- [1.37.7](/php/docs/reference/cloud-firestore/1.37.7/V1.PartitionQueryResponse)\n- [1.36.1](/php/docs/reference/cloud-firestore/1.36.1/V1.PartitionQueryResponse)\n- [1.35.0](/php/docs/reference/cloud-firestore/1.35.0/V1.PartitionQueryResponse)\n- [1.34.0](/php/docs/reference/cloud-firestore/1.34.0/V1.PartitionQueryResponse)\n- [1.33.0](/php/docs/reference/cloud-firestore/1.33.0/V1.PartitionQueryResponse)\n- [1.32.0](/php/docs/reference/cloud-firestore/1.32.0/V1.PartitionQueryResponse)\n- [1.31.0](/php/docs/reference/cloud-firestore/1.31.0/V1.PartitionQueryResponse)\n- [1.30.0](/php/docs/reference/cloud-firestore/1.30.0/V1.PartitionQueryResponse)\n- [1.28.0](/php/docs/reference/cloud-firestore/1.28.0/V1.PartitionQueryResponse)\n- [1.27.3](/php/docs/reference/cloud-firestore/1.27.3/V1.PartitionQueryResponse) \nReference documentation and code samples for the Cloud Firestore V1 Client class PartitionQueryResponse.\n\nThe response for\n[Firestore.PartitionQuery](/php/docs/reference/cloud-firestore/latest/V1.FirestoreClient#_Google_Cloud_Firestore_V1_FirestoreClient__partitionQuery__).\n\nGenerated from protobuf message `google.firestore.v1.PartitionQueryResponse`\n\nNamespace\n---------\n\nGoogle \\\\ Cloud \\\\ Firestore \\\\ V1\n\nMethods\n-------\n\n### __construct\n\nConstructor.\n\n### getPartitions\n\nPartition results.\n\nEach partition is a split point that can be used by RunQuery as a starting\nor end point for the query results. The RunQuery requests must be made with\nthe same query supplied to this PartitionQuery request. The partition\ncursors will be ordered according to same ordering as the results of the\nquery supplied to PartitionQuery.\nFor example, if a PartitionQuery request returns partition cursors A and B,\nrunning the following three queries will return the entire result set of\nthe original query:\n\n- query, end_at A\n- query, start_at A, end_at B\n- query, start_at B An empty result may indicate that the query has too few results to be partitioned, or that the query is not yet supported for partitioning.\n\n### setPartitions\n\nPartition results.\n\nEach partition is a split point that can be used by RunQuery as a starting\nor end point for the query results. The RunQuery requests must be made with\nthe same query supplied to this PartitionQuery request. The partition\ncursors will be ordered according to same ordering as the results of the\nquery supplied to PartitionQuery.\nFor example, if a PartitionQuery request returns partition cursors A and B,\nrunning the following three queries will return the entire result set of\nthe original query:\n\n- query, end_at A\n- query, start_at A, end_at B\n- query, start_at B An empty result may indicate that the query has too few results to be partitioned, or that the query is not yet supported for partitioning.\n\n### getNextPageToken\n\nA page token that may be used to request an additional set of results, up\nto the number specified by `partition_count` in the PartitionQuery request.\n\nIf blank, there are no more results.\n\n### setNextPageToken\n\nA page token that may be used to request an additional set of results, up\nto the number specified by `partition_count` in the PartitionQuery request.\n\nIf blank, there are no more results."]]
