[
https://issues.apache.org/jira/browse/HDDS-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16537571#comment-16537571
]
Hudson commented on HDDS-92:
----------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14547 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/14547/])
HDDS-92. Use DBType during parsing datanode .container files. (hanishakoneru:
rev ee1e0e20368e825a6cef347ed9637c9cf67be45f)
* (edit)
hadoop-hdds/common/src/main/java/org/apache/hadoop/utils/MetadataStoreBuilder.java
* (delete)
hadoop-hdds/common/src/test/java/org/apache/hadoop/ozone/TestMetadataStore.java
* (add)
hadoop-hdds/common/src/test/java/org/apache/hadoop/utils/TestMetadataStore.java
* (edit)
hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/container/common/helpers/KeyUtils.java
* (edit)
hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/container/common/utils/ContainerCache.java
> Use DBType during parsing datanode .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
> Fix For: 0.2.1
>
> Attachments: HDDS-92-HDDS-48.01.patch, HDDS-92-HDDS-48.02.patch,
> HDDS-92-HDDS-48.03.patch, HDDS-92.00.patch
>
>
> 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]
