;a) we have a clear picture of the alternatives and
>b) in the case of backporting, understand how we would ensure quality.
>This is new code that was so far never exposed to the level of testing
>people would expect from 1.6 code.
>
>Michael
>
>On 27.
Hi,
I would like to backport OAK-4933 to 1.6. The impact should be minimal since
the changes are about bringing the AzureBlobStore connector to 1.6.
Changes are:
- new module
- changes in oak-run to support the azure data store
Thanks,
Raul
Hi,
In OAK 1.6, is lastModified of a DataRecord coming a BlobStore (S3, for
example) still used for timestamp comparison? (ex: to detect whether a certain
object needs to be GC-ed). Or updating it can be ignored in backends (like
S3Backend)?
Looking through the code for usage of
Hi,
Please review OAK-4933 ([1]) which adds support for an AzureBlobStore using
Microsoft Azure Blob Storage as underlying storage. Its implementation is
similar to how S3DataStore is implemented.
There is also a PR on GitHub ( [2] ) where the code is split into several
commits to ease
