Storage Blob Data Contributor
(for Shared Access Signature generation) roles, or the Storage Account Key Operator Service Role
(for Account key access) built-in role, or a custom role with permissions to:
Microsoft.Storage/storageAccounts/blobServices/generateUserDelegationKey/action
Microsoft.Storage/storageAccounts/blobServices/containers/blobs/write
Microsoft.Storage/storageAccounts/listkeys/action
+ Container
button to open the New container paneCreate
button...
button on the right and then Generate SAS
Write
Generate SAS token and URL
buttonCopy to clipboard
buttonShow
button next to its connection stringCopy
button to copy the connection string to the clipboardYou don’t have permissions to grant write access. You can still create a shared access signature, but you’ll need an RBAC role with additional permissions before you can grant that level of access to your signature recipient.If so, you need to ensure that your Azure user has been assigned to a built-in Azure role or custom role that has the equivalent permissions to those which you are granting. For granting
Write
access (required by our Connector), your Azure user would need to be assigned to Storage Blob Data Contributor
role or a custom role with the Microsoft.Storage/storageAccounts/blobServices/containers/blobs/write
permission...
button on the right and then Generate SAS
.Write
.Generate SAS token and URL
button.Copy to clipboard
button.JSON
): The format to use when writing the data to file storage.
CSV
format only): Include or exclude column name header row per file.myfolder/subfolder
.
{{topic}}--{{partition}}--{{start_offset}}
): The format of the filename. You can combine any of the elements below using other text or characters, including dashes (-
) and underscores (_
).
Element | Description |
---|---|
{{topic}} | The Streamkap topic name. For example, a PostgreSQL Source table web.salesorders topic’s name would be salesorders . |
{{partition}} | The partition number of the records in the file, typically 0 . Streamkap topics and their data can be partitioned for better performance in certain scenarios. For example, a topic salesorders has 10 partitions, 0 through to 9 . |
{{start_offset}} | The offset number of the first record in the file. Every record streamed has an incrementing offset number. For example, a topic salesorders has 1000 records, offsets 0 through to 999 . Note that in the case of a multi-partitioned topic, offset numbers are not unique across partitions. |
1000
): Number of records to write per file.
65536
): Minimum size (in bytes) per file. Records are held in memory until this file size is met or the Rotate interval is exceeded.
-1
disabled): Maximum time (in milliseconds) to wait before writing records held in memory to file. This ignores the flush and file size settings.
none
): The compression algorithm to use when writing each file. Depending on the Format, some compression algorithms may not be available.
Save
button.