Another fork Lift upgrade of tests

[jayunit100]

src/test/java/org/apache/hadoop/fs/test/unit/HcfsMainOperationsBaseTest.java... prefer FSMainOperationsTests where there is a conflict of behavior (3) confiugrable sorting so that testListStatus can behave the old or new wway, by user preference, (4) umask support, so that hadoop umasks are honored
...

All tests now pass, but we will have to review this full commit when the time is right. The main features are

1. hadoop umask honoring
2. Configurable sort for ListStatus
3. Overriding some FileSystemContract methods, where there are conflicts with competing FSMainOperations test implementations.
4. Imported umask test into Our tests, so that in case we phase out FileSystemContract Tests, we still have umask unit test.
   ...
   0
   Tests run: 50, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 11.344 sec
   Running org.apache.hadoop.fs.test.unit.HcfsFileSystemContractBaseTest
   Tests run: 31, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.348 sec
   Running org.apache.hadoop.fs.test.unit.HcfsFileSystemTest
   Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.117 sec

[childsb]

Where is getScheme() part of the API? Why is it needed?

[jayunit100]

@childsb ~~~~~~~~~~ see below ~~~~~~~~~~~~

$ git status# On branch branch-2.2
nothing to commit, working directory clean

$ cat `find ./ -name FileSystem.java` | grep -A 2 "String getScheme()"

public String getScheme() {
   throw new UnsupportedOperationException("Not implemented by the " + getClass().getSimpleName() + "   
   FileSystem implementation");
}

public String getScheme() {
  return scheme;
}