[
https://issues.apache.org/jira/browse/OAK-8869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17764543#comment-17764543
]
Julian Reschke commented on OAK-8869:
-------------------------------------
trunk: (1.26.0)
[b7bc1a7704|https://github.com/apache/jackrabbit-oak/commit/b7bc1a7704359c721aff77520671bac94f2f4e85]
[954b397def|https://github.com/apache/jackrabbit-oak/commit/954b397def086ed074907d92fc91762169372bdc]
> 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
> Assignee: Andrei Dulceanu
> Priority: Major
> Labels: azureblob, candidate_oak_1_22
> Fix For: 1.26.0
>
> Attachments: OAK-8869-patch1.patch, OAK-8869-patch2.patch,
> OAK-8869-patch3.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.20.10#820010)
