[
https://issues.apache.org/jira/browse/HDDS-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prashant Pogde updated HDDS-1963:
---------------------------------
Target Version/s: 1.2.0
I am managing the 1.1.0 release and we currently have more than 600 issues
targeted for 1.1.0. I am moving the target field to 1.2.0.
If you are actively working on this jira and believe this should be targeted to
1.1.0 release, Please change the target field back to 1.1.0 before Feb 05,
2021.
> OM DB Schema defintion in OmMetadataManagerImpl and OzoneConsts are not
> consistent
> ----------------------------------------------------------------------------------
>
> Key: HDDS-1963
> URL: https://issues.apache.org/jira/browse/HDDS-1963
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Reporter: Sammi Chen
> Priority: Major
>
> OzoneConsts.java
> * OM DB Schema:
> * ----------------------------------------------------------
> * | KEY | VALUE |
> * ----------------------------------------------------------
> * | $userName | VolumeList |
> * ----------------------------------------------------------
> * | /#volumeName | VolumeInfo |
> * ----------------------------------------------------------
> * | /#volumeName/#bucketName | BucketInfo |
> * ----------------------------------------------------------
> * | /volumeName/bucketName/keyName | KeyInfo |
> * ----------------------------------------------------------
> * | #deleting#/volumeName/bucketName/keyName | KeyInfo |
> * ----------------------------------------------------------
> OmMetadataManagerImpl.java
> /**
> * OM RocksDB Structure .
> * <p>
> * OM DB stores metadata as KV pairs in different column families.
> * <p>
> * OM DB Schema:
> * |-------------------------------------------------------------------|
> * | Column Family | VALUE |
> * |-------------------------------------------------------------------|
> * | userTable | user->VolumeList |
> * |-------------------------------------------------------------------|
> * | volumeTable | /volume->VolumeInfo |
> * |-------------------------------------------------------------------|
> * | bucketTable | /volume/bucket-> BucketInfo |
> * |-------------------------------------------------------------------|
> * | keyTable | /volumeName/bucketName/keyName->KeyInfo |
> * |-------------------------------------------------------------------|
> * | deletedTable | /volumeName/bucketName/keyName->KeyInfo |
> * |-------------------------------------------------------------------|
> * | openKey | /volumeName/bucketName/keyName/id->KeyInfo |
> * |-------------------------------------------------------------------|
> * | s3Table | s3BucketName -> /volumeName/bucketName |
> * |-------------------------------------------------------------------|
> * | s3SecretTable | s3g_access_key_id -> s3Secret |
> * |-------------------------------------------------------------------|
> * | dTokenTable | s3g_access_key_id -> s3Secret |
> * |-------------------------------------------------------------------|
> * | prefixInfoTable | prefix -> PrefixInfo |
> * |-------------------------------------------------------------------|
> */
> It's better to put OM DB Schema defintion in one place to resolve this
> inconsistency due to information redundancy.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
