Product DocumentationAppearance
Azure Blob Storage URIs
The ybload client supports several patterns for Azure Blob storage URIs. All of these patterns identify the location of the source data for a bulk load operation. An Azure container (like an S3 bucket) contains one or more "blobs" or "keys." From the point of view of a ybload operation, a blob is effectively a source file. Blobs are stored in "containers."
| URI Pattern | Loads | Example |
|---|---|---|
azure://CONTAINER | All blobs in the container | azure://premdb |
azure://CONTAINER/BLOB | Current version of the named blob | azure://premdb/team01.csv |
azure://CONTAINER/BLOB?snapshot=SNAPSHOT | Specific snapshot (version) of the named blob | azure://premdb/team01.csv?snapshot=2020-04-21T01:59:24.7012660Z |
azure://CONTAINER/BLOB_PREFIX | All blobs that match the prefix | azure://premdb/team |
You can specify multiple URIs on the ybload command line if you want to identify multiple source files explicitly. However, the sources must belong to the same storage account.
URI Parameters
As an alternative to specifying ybload --object-store options, you can specify the Azure configuration in the form of URI parameters. To use a URI parameter, drop the --object-store- prefix from the ybload option name. For example, the --object-store-endpoint option is specified in the following URI as endpoint=:
azure://my_container/my_blob?endpoint=https://mystorageaccount.blob.core.windows.netNote: If you provide multiple source URIs in a single ybload command, only the first URI will be checked for configuration options.
Parent topic:Loading from Azure Blob Storage