• Home
  • Line#
  • Scopes#
  • Navigate#
  • Raw
  • Download
1<html><body>
2<style>
3
4body, h1, h2, h3, div, span, p, pre, a {
5  margin: 0;
6  padding: 0;
7  border: 0;
8  font-weight: inherit;
9  font-style: inherit;
10  font-size: 100%;
11  font-family: inherit;
12  vertical-align: baseline;
13}
14
15body {
16  font-size: 13px;
17  padding: 1em;
18}
19
20h1 {
21  font-size: 26px;
22  margin-bottom: 1em;
23}
24
25h2 {
26  font-size: 24px;
27  margin-bottom: 1em;
28}
29
30h3 {
31  font-size: 20px;
32  margin-bottom: 1em;
33  margin-top: 1em;
34}
35
36pre, code {
37  line-height: 1.5;
38  font-family: Monaco, 'DejaVu Sans Mono', 'Bitstream Vera Sans Mono', 'Lucida Console', monospace;
39}
40
41pre {
42  margin-top: 0.5em;
43}
44
45h1, h2, h3, p {
46  font-family: Arial, sans serif;
47}
48
49h1, h2, h3 {
50  border-bottom: solid #CCC 1px;
51}
52
53.toc_element {
54  margin-top: 0.5em;
55}
56
57.firstline {
58  margin-left: 2 em;
59}
60
61.method  {
62  margin-top: 1em;
63  border: solid 1px #CCC;
64  padding: 1em;
65  background: #EEE;
66}
67
68.details {
69  font-weight: bold;
70  font-size: 14px;
71}
72
73</style>
74
75<h1><a href="firestore_v1beta2.html">Cloud Firestore API</a> . <a href="firestore_v1beta2.projects.html">projects</a> . <a href="firestore_v1beta2.projects.databases.html">databases</a></h1>
76<h2>Instance Methods</h2>
77<p class="toc_element">
78  <code><a href="firestore_v1beta2.projects.databases.collectionGroups.html">collectionGroups()</a></code>
79</p>
80<p class="firstline">Returns the collectionGroups Resource.</p>
81
82<p class="toc_element">
83  <code><a href="#exportDocuments">exportDocuments(name, body, x__xgafv=None)</a></code></p>
84<p class="firstline">Exports a copy of all or a subset of documents from Google Cloud Firestore</p>
85<p class="toc_element">
86  <code><a href="#importDocuments">importDocuments(name, body, x__xgafv=None)</a></code></p>
87<p class="firstline">Imports documents into Google Cloud Firestore. Existing documents with the</p>
88<h3>Method Details</h3>
89<div class="method">
90    <code class="details" id="exportDocuments">exportDocuments(name, body, x__xgafv=None)</code>
91  <pre>Exports a copy of all or a subset of documents from Google Cloud Firestore
92to another storage system, such as Google Cloud Storage. Recent updates to
93documents may not be reflected in the export. The export occurs in the
94background and its progress can be monitored and managed via the
95Operation resource that is created. The output of an export may only be
96used once the associated operation is done. If an export operation is
97cancelled before completion it may leave partial data behind in Google
98Cloud Storage.
99
100Args:
101  name: string, Database to export. Should be of the form:
102`projects/{project_id}/databases/{database_id}`. (required)
103  body: object, The request body. (required)
104    The object takes the form of:
105
106{ # The request for FirestoreAdmin.ExportDocuments.
107    "outputUriPrefix": "A String", # The output URI. Currently only supports Google Cloud Storage URIs of the
108        # form: `gs://BUCKET_NAME[/NAMESPACE_PATH]`, where `BUCKET_NAME` is the name
109        # of the Google Cloud Storage bucket and `NAMESPACE_PATH` is an optional
110        # Google Cloud Storage namespace path. When
111        # choosing a name, be sure to consider Google Cloud Storage naming
112        # guidelines: https://cloud.google.com/storage/docs/naming.
113        # If the URI is a bucket (without a namespace path), a prefix will be
114        # generated based on the start time.
115    "collectionIds": [ # Which collection ids to export. Unspecified means all collections.
116      "A String",
117    ],
118  }
119
120  x__xgafv: string, V1 error format.
121    Allowed values
122      1 - v1 error format
123      2 - v2 error format
124
125Returns:
126  An object of the form:
127
128    { # This resource represents a long-running operation that is the result of a
129      # network API call.
130    "metadata": { # Service-specific metadata associated with the operation.  It typically
131        # contains progress information and common metadata such as create time.
132        # Some services might not provide such metadata.  Any method that returns a
133        # long-running operation should document the metadata type, if any.
134      "a_key": "", # Properties of the object. Contains field @type with type URL.
135    },
136    "error": { # The `Status` type defines a logical error model that is suitable for # The error result of the operation in case of failure or cancellation.
137        # different programming environments, including REST APIs and RPC APIs. It is
138        # used by [gRPC](https://github.com/grpc). The error model is designed to be:
139        #
140        # - Simple to use and understand for most users
141        # - Flexible enough to meet unexpected needs
142        #
143        # # Overview
144        #
145        # The `Status` message contains three pieces of data: error code, error
146        # message, and error details. The error code should be an enum value of
147        # google.rpc.Code, but it may accept additional error codes if needed.  The
148        # error message should be a developer-facing English message that helps
149        # developers *understand* and *resolve* the error. If a localized user-facing
150        # error message is needed, put the localized message in the error details or
151        # localize it in the client. The optional error details may contain arbitrary
152        # information about the error. There is a predefined set of error detail types
153        # in the package `google.rpc` that can be used for common error conditions.
154        #
155        # # Language mapping
156        #
157        # The `Status` message is the logical representation of the error model, but it
158        # is not necessarily the actual wire format. When the `Status` message is
159        # exposed in different client libraries and different wire protocols, it can be
160        # mapped differently. For example, it will likely be mapped to some exceptions
161        # in Java, but more likely mapped to some error codes in C.
162        #
163        # # Other uses
164        #
165        # The error model and the `Status` message can be used in a variety of
166        # environments, either with or without APIs, to provide a
167        # consistent developer experience across different environments.
168        #
169        # Example uses of this error model include:
170        #
171        # - Partial errors. If a service needs to return partial errors to the client,
172        #     it may embed the `Status` in the normal response to indicate the partial
173        #     errors.
174        #
175        # - Workflow errors. A typical workflow has multiple steps. Each step may
176        #     have a `Status` message for error reporting.
177        #
178        # - Batch operations. If a client uses batch request and batch response, the
179        #     `Status` message should be used directly inside batch response, one for
180        #     each error sub-response.
181        #
182        # - Asynchronous operations. If an API call embeds asynchronous operation
183        #     results in its response, the status of those operations should be
184        #     represented directly using the `Status` message.
185        #
186        # - Logging. If some API errors are stored in logs, the message `Status` could
187        #     be used directly after any stripping needed for security/privacy reasons.
188      "message": "A String", # A developer-facing error message, which should be in English. Any
189          # user-facing error message should be localized and sent in the
190          # google.rpc.Status.details field, or localized by the client.
191      "code": 42, # The status code, which should be an enum value of google.rpc.Code.
192      "details": [ # A list of messages that carry the error details.  There is a common set of
193          # message types for APIs to use.
194        {
195          "a_key": "", # Properties of the object. Contains field @type with type URL.
196        },
197      ],
198    },
199    "done": True or False, # If the value is `false`, it means the operation is still in progress.
200        # If `true`, the operation is completed, and either `error` or `response` is
201        # available.
202    "response": { # The normal response of the operation in case of success.  If the original
203        # method returns no data on success, such as `Delete`, the response is
204        # `google.protobuf.Empty`.  If the original method is standard
205        # `Get`/`Create`/`Update`, the response should be the resource.  For other
206        # methods, the response should have the type `XxxResponse`, where `Xxx`
207        # is the original method name.  For example, if the original method name
208        # is `TakeSnapshot()`, the inferred response type is
209        # `TakeSnapshotResponse`.
210      "a_key": "", # Properties of the object. Contains field @type with type URL.
211    },
212    "name": "A String", # The server-assigned name, which is only unique within the same service that
213        # originally returns it. If you use the default HTTP mapping, the
214        # `name` should have the format of `operations/some/unique/name`.
215  }</pre>
216</div>
217
218<div class="method">
219    <code class="details" id="importDocuments">importDocuments(name, body, x__xgafv=None)</code>
220  <pre>Imports documents into Google Cloud Firestore. Existing documents with the
221same name are overwritten. The import occurs in the background and its
222progress can be monitored and managed via the Operation resource that is
223created. If an ImportDocuments operation is cancelled, it is possible
224that a subset of the data has already been imported to Cloud Firestore.
225
226Args:
227  name: string, Database to import into. Should be of the form:
228`projects/{project_id}/databases/{database_id}`. (required)
229  body: object, The request body. (required)
230    The object takes the form of:
231
232{ # The request for FirestoreAdmin.ImportDocuments.
233    "inputUriPrefix": "A String", # Location of the exported files.
234        # This must match the output_uri_prefix of an ExportDocumentsResponse from
235        # an export that has completed successfully.
236        # See:
237        # google.firestore.admin.v1beta2.ExportDocumentsResponse.output_uri_prefix.
238    "collectionIds": [ # Which collection ids to import. Unspecified means all collections included
239        # in the import.
240      "A String",
241    ],
242  }
243
244  x__xgafv: string, V1 error format.
245    Allowed values
246      1 - v1 error format
247      2 - v2 error format
248
249Returns:
250  An object of the form:
251
252    { # This resource represents a long-running operation that is the result of a
253      # network API call.
254    "metadata": { # Service-specific metadata associated with the operation.  It typically
255        # contains progress information and common metadata such as create time.
256        # Some services might not provide such metadata.  Any method that returns a
257        # long-running operation should document the metadata type, if any.
258      "a_key": "", # Properties of the object. Contains field @type with type URL.
259    },
260    "error": { # The `Status` type defines a logical error model that is suitable for # The error result of the operation in case of failure or cancellation.
261        # different programming environments, including REST APIs and RPC APIs. It is
262        # used by [gRPC](https://github.com/grpc). The error model is designed to be:
263        #
264        # - Simple to use and understand for most users
265        # - Flexible enough to meet unexpected needs
266        #
267        # # Overview
268        #
269        # The `Status` message contains three pieces of data: error code, error
270        # message, and error details. The error code should be an enum value of
271        # google.rpc.Code, but it may accept additional error codes if needed.  The
272        # error message should be a developer-facing English message that helps
273        # developers *understand* and *resolve* the error. If a localized user-facing
274        # error message is needed, put the localized message in the error details or
275        # localize it in the client. The optional error details may contain arbitrary
276        # information about the error. There is a predefined set of error detail types
277        # in the package `google.rpc` that can be used for common error conditions.
278        #
279        # # Language mapping
280        #
281        # The `Status` message is the logical representation of the error model, but it
282        # is not necessarily the actual wire format. When the `Status` message is
283        # exposed in different client libraries and different wire protocols, it can be
284        # mapped differently. For example, it will likely be mapped to some exceptions
285        # in Java, but more likely mapped to some error codes in C.
286        #
287        # # Other uses
288        #
289        # The error model and the `Status` message can be used in a variety of
290        # environments, either with or without APIs, to provide a
291        # consistent developer experience across different environments.
292        #
293        # Example uses of this error model include:
294        #
295        # - Partial errors. If a service needs to return partial errors to the client,
296        #     it may embed the `Status` in the normal response to indicate the partial
297        #     errors.
298        #
299        # - Workflow errors. A typical workflow has multiple steps. Each step may
300        #     have a `Status` message for error reporting.
301        #
302        # - Batch operations. If a client uses batch request and batch response, the
303        #     `Status` message should be used directly inside batch response, one for
304        #     each error sub-response.
305        #
306        # - Asynchronous operations. If an API call embeds asynchronous operation
307        #     results in its response, the status of those operations should be
308        #     represented directly using the `Status` message.
309        #
310        # - Logging. If some API errors are stored in logs, the message `Status` could
311        #     be used directly after any stripping needed for security/privacy reasons.
312      "message": "A String", # A developer-facing error message, which should be in English. Any
313          # user-facing error message should be localized and sent in the
314          # google.rpc.Status.details field, or localized by the client.
315      "code": 42, # The status code, which should be an enum value of google.rpc.Code.
316      "details": [ # A list of messages that carry the error details.  There is a common set of
317          # message types for APIs to use.
318        {
319          "a_key": "", # Properties of the object. Contains field @type with type URL.
320        },
321      ],
322    },
323    "done": True or False, # If the value is `false`, it means the operation is still in progress.
324        # If `true`, the operation is completed, and either `error` or `response` is
325        # available.
326    "response": { # The normal response of the operation in case of success.  If the original
327        # method returns no data on success, such as `Delete`, the response is
328        # `google.protobuf.Empty`.  If the original method is standard
329        # `Get`/`Create`/`Update`, the response should be the resource.  For other
330        # methods, the response should have the type `XxxResponse`, where `Xxx`
331        # is the original method name.  For example, if the original method name
332        # is `TakeSnapshot()`, the inferred response type is
333        # `TakeSnapshotResponse`.
334      "a_key": "", # Properties of the object. Contains field @type with type URL.
335    },
336    "name": "A String", # The server-assigned name, which is only unique within the same service that
337        # originally returns it. If you use the default HTTP mapping, the
338        # `name` should have the format of `operations/some/unique/name`.
339  }</pre>
340</div>
341
342</body></html>