Skip to content

HDFS-16541. Fix a typo in NameNodeLayoutVersion #4176

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 18, 2022
Merged

HDFS-16541. Fix a typo in NameNodeLayoutVersion #4176

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b3f4eee
Fix typo for NameNodeLayoutVersion.
Happy-shi Apr 14, 2022
c73058a
HDFS-16541. Fix some typo in NameNodeLayoutVersion
Happy-shi Apr 15, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions ...doop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNodeLayoutVersion.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,10 +66,10 @@ public static boolean supports(final LayoutFeature f, final int lv) {
* 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
Expand Down Expand Up @@ -98,15 +98,15 @@ public enum Feature implements LayoutFeature {
/**
* 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) {
this(lv, lv + 1, minCompatLV, description, false);
}

/**
* 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
Expand Down