[ 
https://issues.apache.org/jira/browse/CAMEL-19254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709359#comment-17709359
 ] 

Idorasi Paul edited comment on CAMEL-19254 at 4/6/23 12:21 PM:
---------------------------------------------------------------

On further digging, I found out the issue. I tried comparing the azure blob 
versions, I thought the usage of etag for concurrency consistency was added 
between version 12.14.4 and 12.16.0, but I was wrong, etag check was there for 
a long time. What was actually changed and what is causing this issue is the 
stream caching being enabled by default. The default behaviour was changed 
between camel-azure 3.16.0 and 3.17.0. Turning off stream caching will fix the 
issue. Not sure why to be honest...


was (Author: JIRAUSER299619):
On further digging, I found out the issue. I tried comparing the azure blob 
versions, I thought the usage of etag for concurrency consistency was added 
between version 12.14.4 and 12.16.0, but I was wrong, etag check was there for 
a long time. What was actually changed and was is causing this issue is the 
stream caching being enabled by default. The default behaviour was changed 
between camel-azure 3.16.0 and 3.17.0. Turning off stream caching will fix the 
issue. Not sure why to be honest...

> Azure Blob file download conditionNotMet error
> ----------------------------------------------
>
>                 Key: CAMEL-19254
>                 URL: https://issues.apache.org/jira/browse/CAMEL-19254
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-azure
>    Affects Versions: 3.17.0, 3.18.0, 3.19.0, 3.20.3
>            Reporter: Idorasi Paul
>            Priority: Major
>
> When downloading blobs using the camel component a ConditionNotMet exception 
> is thrown. The condition that is not met is the if-match condition that 
> contains the etag value of the blob. When endpoint polls the file, it 
> attempts to download it in chunks. During the download, if the file is 
> touched, the etag changes and the download fails, after that everything goes 
> to hell. This does not happens on local, I think that downloading the file is 
> much, much faster and this concurrency issue does not occur, but as soon as 
> you switch to a real azure environment the issue will occur every time. To 
> reproduce the error follow the steps: 
>  # Start application in debug mode
>  # Add a breakpoint on StorageInputStream at line 317
>  # Skip first chunk download
>  # Go to azure blob and touch the file (add new metadata) 
>  # Skip second chunk download
>  # Exception is thrown
>  
> Last version that works without this issue is 3.16.0
> [Zulip chat 
> topic|https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/CamelAzureBlob.20endpoint.20prefix]



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

Reply via email to