[BEAM-2369] HadoopFileSystem: NullPointerException on match of non existing resource

• Type: Bug
• Status: Resolved
• Priority: P2
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.1.0
• Component/s: io-java-hadoop-file-system
• Assignee: Michael Luckey
• Reporter: Michael Luckey
• Created: 26/May/17 13:18
• Updated: 16/May/20 13:53
• Resolved: 26/May/17 23:27

Description

Testcase:

  @Test
  public void testMatchForNonExistentFile() throws Exception {
    create("testFileAA", "testDataAA".getBytes());

    // ensure files exist
    assertArrayEquals("testDataAA".getBytes(), read("testFileAA"));

    List<MatchResult> matchResults = fileSystem.match(
            ImmutableList.of(testPath("testFileA").toString()));
    assertEquals(Status.NOT_FOUND, Iterables.getOnlyElement(matchResults).status());
  }

throws NullPointerException

java.lang.NullPointerException
	at org.apache.beam.sdk.io.hdfs.HadoopFileSystem.match(HadoopFileSystem.java:87)
	at org.apache.beam.sdk.io.hdfs.HadoopFileSystemTest.testMatchForNonExistentFile(HadoopFileSystemTest.java:187)

as the underlying hadoop implementation returns null:

     * When the input pattern "looks" like just a simple filename, and we
     * can't find it, we return null rather than an empty array.
     * This is a special case which the shell relies on.

Issue Links

• links to: GitHub Pull Request #3237