+1 for creating the issue and attaching there the patch Regards, Andrei
On Thu, Jan 23, 2020 at 11:21 AM Tomek Rękawek <tom...@apache.org> wrote: > Hi Aravindo, > > I’m in favour of merging the patch. I think being strict in what we write > and tolerant in what we read is a good thing. Please create an OAK issue > and ping me and Andrei Dulceanu, so we can merge it. > > Regards, > Tomek > > -- > Tomek Rękawek | ASF committer | www.apache.org > tom...@apache.org > > > On 23 Jan 2020, at 11:08, Aravindo Wingeier <winge...@adobe.com> wrote: > > > > Hi dev's, > > > > 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 am contacting MS > directly to follow up on this. As an alternative, we currently use azcopy > version 7, which is much slower and has reliability issues. > > > > 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. See the patch draft at [2]. > > > > What do you think is the best way to go forward? > > > > Best regards, > > > > Aravindo Wingeier > > > > [1]: https://github.com/Azure/azure-storage-azcopy/issues/113 > > [2]: https://github.com/apache/jackrabbit-oak/pull/173 > >
