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 "Andrei Dulceanu (JIRA)" <ji...@apache.org> on 2018/07/23 09:02:00 UTC
[jira] [Resolved] (OAK-7623) SegmentNodeStore - sidegrade support
between TarPersistence and AzurePersistence
[ https://issues.apache.org/jira/browse/OAK-7623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Dulceanu resolved OAK-7623.
----------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.9.0)
1.9.7
Thanks for the quick review, [~tomek.rekawek]!
Fixed at r1836474.
> SegmentNodeStore - sidegrade support between TarPersistence and AzurePersistence
> --------------------------------------------------------------------------------
>
> Key: OAK-7623
> URL: https://issues.apache.org/jira/browse/OAK-7623
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: segment-tar, upgrade
> Reporter: Andrei Dulceanu
> Assignee: Andrei Dulceanu
> Priority: Major
> Labels: azure, migration
> Fix For: 1.10, 1.9.7
>
> Attachments: OAK-7623.patch
>
>
> Azure support for segment-tar (OAK-6922) allowed us to plug another storage option for the segment store. Since sometimes there's the need to compare how local vs remote storage behaves, a sidegrade from local tar storage to remote azure storage must be implemented.
> This would allow us to replicate the exact repository content, changing only the underlying storage mechanism. Analogous to OAK-7459, the Azure Segment Store connection details will be supplied in the following format:
> * an URI with the following format: {{az:[https://myaccount.blob.core.windows.net/container/repo]}}, where _az_ identifies the cloud provider
> * a secret key supplied as an environment variable, i.e. _AZURE_SECRET_KEY._
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)