[ 
https://issues.apache.org/jira/browse/CAMEL-23331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino resolved CAMEL-23331.
--------------------------------------
    Resolution: Fixed

> camel-azure-storage-blob - Add support for blob snapshot creation and 
> retrieval
> -------------------------------------------------------------------------------
>
>                 Key: CAMEL-23331
>                 URL: https://issues.apache.org/jira/browse/CAMEL-23331
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-azure
>            Reporter: Andrea Cosentino
>            Assignee: Andrea Cosentino
>            Priority: Major
>             Fix For: 4.20.0
>
>
> The camel-azure-storage-blob component currently only handles snapshots 
> during blob deletion (via DeleteSnapshotsOptionType). It lacks the ability to 
> create snapshots or access blobs at a specific snapshot.
> The Azure SDK provides BlobClient.createSnapshot(), 
> BlobClient.createSnapshotWithResponse(), and BlobClientBuilder.snapshot() for 
> full snapshot support.
> *Add:*
> - A createBlobSnapshot producer operation that creates a point-in-time 
> snapshot via BlobClient.createSnapshotWithResponse(), returning the snapshot 
> ID in exchange headers
> - A snapshotId parameter (on BlobConfiguration and as a header) so that read 
> operations (getBlob, downloadBlobToFile, downloadLink) can target a specific 
> snapshot
> *Implementation scope:*
> - Add createBlobSnapshot to BlobOperationsDefinition
> - Add snapshotId @UriParam to BlobConfiguration
> - Add SNAPSHOT_ID and SNAPSHOT_METADATA header constants to BlobConstants
> - Add createSnapshot() wrapper to BlobClientWrapper
> - Modify blob client creation path to support snapshot targeting (similar to 
> version ID)
> - Add operation implementation in BlobOperations
> - Wire operation in BlobProducer
> - Update BlobExchangeHeaders with snapshot ID from responses
> - Update documentation and add tests



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to