You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-commits@hadoop.apache.org by ay...@apache.org on 2022/04/18 17:24:09 UTC

[hadoop] branch trunk updated: HDFS-16541. Fix a typo in NameNodeLayoutVersion (#4176)

This is an automated email from the ASF dual-hosted git repository.

ayushsaxena pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/hadoop.git


The following commit(s) were added to refs/heads/trunk by this push:
     new f74f2416369 HDFS-16541. Fix a typo in NameNodeLayoutVersion (#4176)
f74f2416369 is described below

commit f74f24163692087d7fa7a04e93ed24bca4569a7a
Author: Happy-shi <35...@users.noreply.github.com>
AuthorDate: Tue Apr 19 01:23:57 2022 +0800

    HDFS-16541. Fix a typo in NameNodeLayoutVersion (#4176)
---
 .../apache/hadoop/hdfs/server/namenode/NameNodeLayoutVersion.java | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNodeLayoutVersion.java b/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNodeLayoutVersion.java
index f5e261dc78a..8dfc3111a6b 100644
--- a/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNodeLayoutVersion.java
+++ b/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNodeLayoutVersion.java
@@ -66,10 +66,10 @@ public class NameNodeLayoutVersion {
    * layout version is the earliest prior version to which a downgrade is
    * possible after initiating rolling upgrade.  If the feature cannot satisfy
    * compatibility with any prior version, then set its minimum compatible
-   * lqyout version to itself to indicate that downgrade is impossible.
+   * layout version to itself to indicate that downgrade is impossible.
    * Satisfying compatibility might require adding logic to the new feature to
    * reject operations or handle them differently while rolling upgrade is in
-   * progress.  In general, it's possible to satisfy compatiblity for downgrade
+   * progress.  In general, it's possible to satisfy compatibility for downgrade
    * if the new feature just involves adding new edit log ops.  Deeper
    * structural changes, such as changing the way we place files in the metadata
    * directories, might be incompatible.  Feature implementations should strive
@@ -98,7 +98,7 @@ public class NameNodeLayoutVersion {
     /**
      * Feature that is added at layout version {@code lv} - 1. 
      * @param lv new layout version with the addition of this feature
-     * @param minCompatLV minimium compatible layout version
+     * @param minCompatLV minimum compatible layout version
      * @param description description of the feature
      */
     Feature(final int lv, int minCompatLV, final String description) {
@@ -106,7 +106,7 @@ public class NameNodeLayoutVersion {
     }
 
     /**
-     * NameNode feature that is added at layout version {@code ancestoryLV}.
+     * NameNode feature that is added at layout version {@code ancestorLV}.
      * @param lv new layout version with the addition of this feature
      * @param ancestorLV layout version from which the new lv is derived from.
      * @param minCompatLV minimum compatible layout version


---------------------------------------------------------------------
To unsubscribe, e-mail: common-commits-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-commits-help@hadoop.apache.org