[
https://issues.apache.org/jira/browse/HDDS-13750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Andika updated HDDS-13750:
-------------------------------
Description:
Currently, rename operations can only be done within the same bucket.
Cross-bucket atomic rename within an OM service is technically possible since a
single OM service only shares identical OM DB which supports atomic WriteBatch.
>From what I understand, there are a possible reasons for the restriction
>({*}please{*} *kindly* *suggest more if there are more historical reasons of*
>{*}this{*}) :
* There might be incompatible bucket layout differences between the two
buckets (e.g. OBS -> FSO, vice versa)
* Renaming within a single bucket is simpler (no need to update quota,
permission checks, etc)
We can try to support the cross-bucket renames. We might create a new Rename V2
OM request for compatibility reason. Note that cross-service renames would
still be rejected.
One use case is to implement a policy where all the keys in trash are moved to
a separate bucket so that trash keys are not counted in the bucket quota usage.
was:
Currently, rename operations can only be done within the same bucket.
Cross-bucket atomic rename within an OM service is technically possible since a
single OM service only shares identical OM DB which supports atomic WriteBatch.
>From what I understand, there are a possible reasons for the restriction
>({*}please{*} *kindly* *suggest more if there are more historical reasons of*
>{*}this{*}) :
* There might be incompatible bucket layout differences between the two
buckets (e.g. OBS -> FSO, vice versa)
* Renaming within a single bucket is simpler (no need to update quota,
permission checks, etc)
We can try to support the cross-bucket renames. We might create a new Rename V2
OM request for compatibility reason. Note that cross-service renames would
still be rejected.
> Cross-bucket rename operations
> ------------------------------
>
> Key: HDDS-13750
> URL: https://issues.apache.org/jira/browse/HDDS-13750
> Project: Apache Ozone
> Issue Type: New Feature
> Reporter: Ivan Andika
> Assignee: Ivan Andika
> Priority: Major
>
> Currently, rename operations can only be done within the same bucket.
> Cross-bucket atomic rename within an OM service is technically possible since
> a single OM service only shares identical OM DB which supports atomic
> WriteBatch.
> From what I understand, there are a possible reasons for the restriction
> ({*}please{*} *kindly* *suggest more if there are more historical reasons of*
> {*}this{*}) :
> * There might be incompatible bucket layout differences between the two
> buckets (e.g. OBS -> FSO, vice versa)
> * Renaming within a single bucket is simpler (no need to update quota,
> permission checks, etc)
> We can try to support the cross-bucket renames. We might create a new Rename
> V2 OM request for compatibility reason. Note that cross-service renames would
> still be rejected.
> One use case is to implement a policy where all the keys in trash are moved
> to a separate bucket so that trash keys are not counted in the bucket quota
> usage.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
