pub struct ProjectLocationDatasetHl7V2StoreImportCall<'a, S>where
S: 'a,{ /* private fields */ }Expand description
Import messages to the HL7v2 store by loading data from the specified sources. This method is optimized to load large quantities of data using import semantics that ignore some HL7v2 store configuration options and are not suitable for all use cases. It is primarily intended to load data into an empty HL7v2 store that is not being used by other clients. An existing message will be overwritten if a duplicate message is imported. A duplicate message is a message with the same raw bytes as a message that already exists in this HL7v2 store. When a message is overwritten, its labels will also be overwritten. The import operation is idempotent unless the input data contains multiple valid messages with the same raw bytes but different labels. In that case, after the import completes, the store contains exactly one message with those raw bytes but there is no ordering guarantee on which version of the labels it has. The operation result counters do not count duplicated raw bytes as an error and count one success for each message in the input, which might result in a success count larger than the number of messages in the HL7v2 store. If some messages fail to import, for example due to parsing errors, successfully imported messages are not rolled back. This method returns an Operation that can be used to track the status of the import by calling GetOperation. Immediate fatal errors appear in the error field, errors are also logged to Cloud Logging (see Viewing error logs in Cloud Logging). Otherwise, when the operation finishes, a response of type ImportMessagesResponse is returned in the response field. The metadata field type for this operation is OperationMetadata.
A builder for the locations.datasets.hl7V2Stores.import method supported by a project resource.
It is not used directly, but through a ProjectMethods instance.
§Example
Instantiate a resource method builder
use healthcare1_beta1::api::ImportMessagesRequest;
// As the method needs a request, you would usually fill it with the desired information
// into the respective structure. Some of the parts shown here might not be applicable !
// Values shown here are possibly random and not representative !
let mut req = ImportMessagesRequest::default();
// You can configure optional parameters by calling the respective setters at will, and
// execute the final call using `doit()`.
// Values shown here are possibly random and not representative !
let result = hub.projects().locations_datasets_hl7_v2_stores_import(req, "name")
.doit().await;Implementations§
source§impl<'a, S> ProjectLocationDatasetHl7V2StoreImportCall<'a, S>
impl<'a, S> ProjectLocationDatasetHl7V2StoreImportCall<'a, S>
sourcepub async fn doit(self) -> Result<(Response<Body>, Operation)>
pub async fn doit(self) -> Result<(Response<Body>, Operation)>
Perform the operation you have build so far.
sourcepub fn request(
self,
new_value: ImportMessagesRequest
) -> ProjectLocationDatasetHl7V2StoreImportCall<'a, S>
pub fn request( self, new_value: ImportMessagesRequest ) -> ProjectLocationDatasetHl7V2StoreImportCall<'a, S>
Sets the request property to the given value.
Even though the property as already been set when instantiating this call, we provide this method for API completeness.
sourcepub fn name(
self,
new_value: &str
) -> ProjectLocationDatasetHl7V2StoreImportCall<'a, S>
pub fn name( self, new_value: &str ) -> ProjectLocationDatasetHl7V2StoreImportCall<'a, S>
Required. The name of the target HL7v2 store, in the format projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/hl7v2Stores/{hl7v2_store_id}
Sets the name path property to the given value.
Even though the property as already been set when instantiating this call, we provide this method for API completeness.
sourcepub fn delegate(
self,
new_value: &'a mut dyn Delegate
) -> ProjectLocationDatasetHl7V2StoreImportCall<'a, S>
pub fn delegate( self, new_value: &'a mut dyn Delegate ) -> ProjectLocationDatasetHl7V2StoreImportCall<'a, S>
The delegate implementation is consulted whenever there is an intermediate result, or if something goes wrong while executing the actual API request.
It should be used to handle progress information, and to implement a certain level of resilience.
Sets the delegate property to the given value.
sourcepub fn param<T>(
self,
name: T,
value: T
) -> ProjectLocationDatasetHl7V2StoreImportCall<'a, S>
pub fn param<T>( self, name: T, value: T ) -> ProjectLocationDatasetHl7V2StoreImportCall<'a, S>
Set any additional parameter of the query string used in the request. It should be used to set parameters which are not yet available through their own setters.
Please note that this method must not be used to set any of the known parameters which have their own setter method. If done anyway, the request will fail.
§Additional Parameters
- $.xgafv (query-string) - V1 error format.
- access_token (query-string) - OAuth access token.
- alt (query-string) - Data format for response.
- callback (query-string) - JSONP
- fields (query-string) - Selector specifying which fields to include in a partial response.
- key (query-string) - API key. Your API key identifies your project and provides you with API access, quota, and reports. Required unless you provide an OAuth 2.0 token.
- oauth_token (query-string) - OAuth 2.0 token for the current user.
- prettyPrint (query-boolean) - Returns response with indentations and line breaks.
- quotaUser (query-string) - Available to use for quota purposes for server-side applications. Can be any arbitrary string assigned to a user, but should not exceed 40 characters.
- uploadType (query-string) - Legacy upload protocol for media (e.g. “media”, “multipart”).
- upload_protocol (query-string) - Upload protocol for media (e.g. “raw”, “multipart”).
sourcepub fn add_scope<St>(
self,
scope: St
) -> ProjectLocationDatasetHl7V2StoreImportCall<'a, S>
pub fn add_scope<St>( self, scope: St ) -> ProjectLocationDatasetHl7V2StoreImportCall<'a, S>
Identifies the authorization scope for the method you are building.
Use this method to actively specify which scope should be used, instead of the default Scope variant
Scope::CloudHealthcare.
The scope will be added to a set of scopes. This is important as one can maintain access
tokens for more than one scope.
Usually there is more than one suitable scope to authorize an operation, some of which may encompass more rights than others. For example, for listing resources, a read-only scope will be sufficient, a read-write scope will do as well.
sourcepub fn add_scopes<I, St>(
self,
scopes: I
) -> ProjectLocationDatasetHl7V2StoreImportCall<'a, S>
pub fn add_scopes<I, St>( self, scopes: I ) -> ProjectLocationDatasetHl7V2StoreImportCall<'a, S>
Identifies the authorization scope(s) for the method you are building.
See Self::add_scope() for details.
sourcepub fn clear_scopes(self) -> ProjectLocationDatasetHl7V2StoreImportCall<'a, S>
pub fn clear_scopes(self) -> ProjectLocationDatasetHl7V2StoreImportCall<'a, S>
Removes all scopes, and no default scope will be used either.
In this case, you have to specify your API-key using the key parameter (see Self::param()
for details).