Azure Blob Storage output buffer size, in megabytes. Example: 5
Format specific configuration. See below for details.
⚠️ Please note that under "Full Refresh Sync" mode, data in the configured blob will be wiped out before each sync. We recommend you to provision a dedicated Azure Blob Storage Container resource for this sync to prevent unexpected data deletion from misconfiguration. ⚠️
Each stream will be outputted to its dedicated Blob according to the configuration. The complete datastore of each stream includes all the output files under that Blob. You can think of the Blob as equivalent of a Table in the database world.
Under Full Refresh Sync mode, old output files will be purged before new files are created.
Under Incremental - Append Sync mode, new output files will be added that only contain the new data.
Like most of the other Airbyte destination connectors, usually the output has three columns: a UUID, an emission timestamp, and the data blob. With the CSV output, it is possible to normalize (flatten) the data blob to multiple columns.
A uuid assigned by Airbyte to each processed record.
A timestamp representing when the event was pulled from the data source.
When no normalization (flattening) is needed, all data reside under this column as a json blob.
root level fields
When root level normalization (flattening) is selected, the root level fields are expanded.
For example, given the following json object from a source: