Network.Google.Resource.Genomics.Variants.Import

Creates variant data by asynchronously importing the provided information. The variants for import will be merged with any existing variant that matches its reference sequence, start, end, reference bases, and alternative bases. If no such variant exists, a new one will be created. When variants are merged, the call information from the new variant is added to the existing variant, and other fields (such as key/value pairs) are discarded. In particular, this means for merged VCF variants that have conflicting INFO fields, some data will be arbitrarily discarded. As a special case, for single-sample VCF files, QUAL and FILTER fields will be moved to the call level; these are sometimes interpreted in a call-specific context. Imported VCF headers are appended to the metadata already in a variant set.

See: API Reference for genomics.variants.import.

REST Resource

type VariantsImportResource = "v1" :> ("variants:import" :> (QueryParam "$.xgafv" Text :> (QueryParam "upload_protocol" Text :> (QueryParam "pp" Bool :> (QueryParam "access_token" Text :> (QueryParam "uploadType" Text :> (QueryParam "bearer_token" Text :> (QueryParam "callback" Text :> (QueryParam "alt" AltJSON :> (ReqBody `[JSON]` ImportVariantsRequest :> Post `[JSON]` Operation))))))))))

A resource alias for genomics.variants.import method which the VariantsImport request conforms to.

Creating a Request

variantsImport

Arguments

:: ImportVariantsRequest

viPayload

-> VariantsImport

Creates a value of VariantsImport with the minimum fields required to make a request.

Use one of the following lenses to modify other fields as desired:

• viXgafv
• viUploadProtocol
• viPp
• viAccessToken
• viUploadType
• viPayload
• viBearerToken
• viCallback

data VariantsImport

Creates variant data by asynchronously importing the provided information. The variants for import will be merged with any existing variant that matches its reference sequence, start, end, reference bases, and alternative bases. If no such variant exists, a new one will be created. When variants are merged, the call information from the new variant is added to the existing variant, and other fields (such as key/value pairs) are discarded. In particular, this means for merged VCF variants that have conflicting INFO fields, some data will be arbitrarily discarded. As a special case, for single-sample VCF files, QUAL and FILTER fields will be moved to the call level; these are sometimes interpreted in a call-specific context. Imported VCF headers are appended to the metadata already in a variant set.

See: variantsImport smart constructor.

Instances

Eq VariantsImport

Data VariantsImport

Show VariantsImport

Generic VariantsImport

GoogleRequest VariantsImport

type Rep VariantsImport

type Rs VariantsImport = Operation

Request Lenses

viXgafv :: Lens' VariantsImport (Maybe Text)

V1 error format.

viUploadProtocol :: Lens' VariantsImport (Maybe Text)

Upload protocol for media (e.g. "raw", "multipart").

viPp :: Lens' VariantsImport Bool

Pretty-print response.

viAccessToken :: Lens' VariantsImport (Maybe Text)

OAuth access token.

viUploadType :: Lens' VariantsImport (Maybe Text)

Legacy upload protocol for media (e.g. "media", "multipart").

viPayload :: Lens' VariantsImport ImportVariantsRequest

Multipart request metadata.

viBearerToken :: Lens' VariantsImport (Maybe Text)

OAuth bearer token.

viCallback :: Lens' VariantsImport (Maybe Text)

JSONP