[
https://issues.apache.org/jira/browse/HDDS-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16907273#comment-16907273
]
Anu Engineer commented on HDDS-1963:
------------------------------------
Agree, Thanks for flagging this. Perhaps the OmMetadataManagerImpl is the way
to go?
> 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
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
