[
https://issues.apache.org/jira/browse/HDDS-5372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17451556#comment-17451556
]
Rakesh Radhakrishnan commented on HDDS-5372:
--------------------------------------------
[~aryangupta1998] please refer
[PR-2764|https://github.com/apache/ozone/pull/2764] to automate this case.
Also, refer
[xcompat/test.sh|https://github.com/apache/ozone/blob/master/hadoop-ozone/dist/src/main/compose/xcompat/test.sh]
robo test.
*+Pre-requisite:+* Set ozone.om.enable.filesystem.paths=true in OM
step-1) start an old cluster with version 1.1.0
step-2) create bucket "vol1/buck1" using old_client version 1.1.0.
step-3) create dir structure "vol1/buck1/dir1/dir2" using old_client version
1.1.0.
step-4) create file "vol1/buck1/dir1/dir2/file-1" using old_client version
1.1.0.
step-5) start a new cluster with master current version 1.3.0 using the old
cluster's 1.1.0 om.db directory.
step-6) create file "vol1/buck1/dir1/dir2/file-2" using new_client version
1.3.0.
step-7) perform list/rename key operations using new_client 1.3.0., current
master version.
> [FSO] Provide mechanism to read and write keys to old bucket
> ------------------------------------------------------------
>
> Key: HDDS-5372
> URL: https://issues.apache.org/jira/browse/HDDS-5372
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: Ozone Manager
> Reporter: Aryan Gupta
> Assignee: Aryan Gupta
> Priority: Major
>
> Currently old buckets(already present in DB) don't have any bucket type. We
> have introduced a Jira which enables bucket types(FSO, OBJRCT_STORE, and
> LEGACY as of now). So, after the upgrade, old buckets will be mapped to
> LEGACY bucket type and it will allow the client to access (read/write) keys
> into it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
