You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Aravindo Wingeier (Jira)" <ji...@apache.org> on 2020/01/24 15:24:00 UTC
[jira] [Commented] (OAK-8869) Access azure segments metadata in a
case-insensitive way
[ https://issues.apache.org/jira/browse/OAK-8869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17023018#comment-17023018 ]
Aravindo Wingeier commented on OAK-8869:
----------------------------------------
[~tomekr], [~adulceanu] please review
also visible at [https://github.com/apache/jackrabbit-oak/pull/173]
> Access azure segments metadata in a case-insensitive way
> --------------------------------------------------------
>
> Key: OAK-8869
> URL: https://issues.apache.org/jira/browse/OAK-8869
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: segment-azure
> Affects Versions: 1.8.19
> Reporter: Aravindo Wingeier
> Priority: Major
> Labels: azureblob
> Attachments: OAK-8869-patch1.patch
>
>
> We use azcopy to copy segments from one azure blob container to another for testing. There is a bug in the current version of azcopy (10.3.3), which makes all metadata keys start with a capital letter - "type" becomes "Type". As a consequence, the current implementation can not find the segments in the azure blob storage.
>
> The azcopy issue was already reported [1] in 2018. I have little hope that azcopy will be fixed soon.
>
> Therefore I suggest a patch to oak-segment-azure, that would be backward compatible and ignore the case of the keys when reading metadata. We should be strict in what we write and tolerant in what we read.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)