[ 
https://issues.apache.org/jira/browse/HDDS-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bharat Viswanadham updated HDDS-92:
-----------------------------------
    Description: 
Now with HDDS-71, when container is created we store containerDBType 
information in .container file.

Use containerDBType which is stored in .container files during parsing of 
.container files.

If intially during cluster setup we use ozone.metastore.impl as default, and 
later changed the ozone.metastore.impl, with current code, we will not be able 
to read those container's.

With this Jira, we can address this.

  was:
Now with HDDS-71, when container is created we store containerDBType 
information in .container file.

Use containerDBType which is stored in .container files during parsing of 
.container files.

If intially during clustersetup we use ozone.metastore.impl as default, and 
later changed the ozone.metastore.impl

default metaNow with this, we can support if containerDBType is changed later


> Use containerDBType during parsing .container files
> ---------------------------------------------------
>
>                 Key: HDDS-92
>                 URL: https://issues.apache.org/jira/browse/HDDS-92
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>          Components: Ozone Datanode
>            Reporter: Bharat Viswanadham
>            Assignee: Bharat Viswanadham
>            Priority: Major
>
> Now with HDDS-71, when container is created we store containerDBType 
> information in .container file.
> Use containerDBType which is stored in .container files during parsing of 
> .container files.
> If intially during cluster setup we use ozone.metastore.impl as default, and 
> later changed the ozone.metastore.impl, with current code, we will not be 
> able to read those container's.
> With this Jira, we can address this.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to