Azure Blob storage data source
This article provides an introduction to how Upsolver works with Azure Blob storage along with a guide on how to create an Azure Blob storage data source in Upsolver.
Last updated
This article provides an introduction to how Upsolver works with Azure Blob storage along with a guide on how to create an Azure Blob storage data source in Upsolver.
Last updated
Upsolver can read events directly from your Azure Blob storage, assuming events are partitioned by event date (this partitioning defines the folder structure in the cloud storage).
Upsolver auto-detects the file format's date pattern and shows you a preview of the top files that will be ingested with their corresponding dates. It also auto-detects when to start the ingestion from.
1. From the Data Sources, click New.
2. Select Azure Blob Storage.
As you fill in the fields, the top matching files with their dates appear in the Preview pane on the right.
indicates that the file is recognized and will be included in the data source ingestion.
indicates that the file will not be included.
You can click Refresh to check on their status as you update fields.
3. Select the Azure Blob storage connection to read from (or create a new one).
4. (Optional) Enter the path to the data folder in Azure Blob storage (e.g. billing data). If this is not specified, the data is assumed to be in the top-level of the hierarchy.
Upsolver adds an implicit / before and after the folder.
For example, if you have bucket a, with folder b, Upsolver looks for the path: s3://a/b/yyyy-MM-dd
The full path displayed is read only. You can use it to review the path Upsolver is using to read from S3.
5. Select or enter in the date pattern of the files to be ingested. This is autodetected but can be modified if required.
The following characters are valid: yyyy MM dd HH mm
Any other letters or characters must be wrapped in single quotes
(e.g. 'year='yyyy'month='MM'day='dd'hour='HH'minutes='mm).
It is also possible to specify the date as follows: d-M-yy
6. (Optional) Select a time to start ingesting files from. This is usually auto detected, but if there is no preview, the date cannot be established and this defaults to today's date. In this case, set the required start date.
7. (Optional) Under File Name Pattern, select the type of pattern to use (All, Starts With, Ends With, Regular Expression, or Glob Expression) and then enter the file name pattern that specifies the file set to ingest.
If all the files in specified folders are relevant, select All.
The pattern given is matched against the file path starting from the full path shown above.
8. Select the content format. This is typically auto-detected, but you can manually select a format.
If necessary, configure the content format options. See: Data formats
9. From the dropdown, select a compute cluster (or create a new one) to run the calculation on.
For production environments, this indicates that if you run your task retroactively (Start Ingestion From), your compute cluster will process a burst of additional tasks, possibly causing delays in outputs and lookup tables running on this cluster.
To prevent this, go to the Clusters page to edit your cluster and set the Additional Processing Units For Replay to a number greater than 0.
10. Select a target storage connection (or create a new one) where the data read will be stored (output storage).
11. (Optional) In addition to the streaming data, you may have initial data. In this case, to list the relevant data, enter a file name prefix (e.g. for DMS loads, enter LOAD) under Initial Load Configuration.
12. (Optional) Under Initial Load Configuration, enter a regex pattern to select the required files.
13. Name this data source.
14. Click Continue. A preview of the data will appear.
15. For CSV, select a Header.
16. Click Continue again.
Parsed data samples will appear and you can review the Sample Size, Parsed Successfully, and # of Errors.
17. (Optional) If there are any errors, click Back to change the settings as required.
18. Click Create.
You can now use your Azure Blob storage data source.
A may appear. This warning can be ignored for POCs (proof of concept).
