[AVRO-1249] DataFileWriter doesn't correctly conform to Closeable

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.7.3
• Fix Version/s: 1.7.4
• Component/s: java
• Hadoop Flags: Incompatible change
• Release Note: DataFileWriter#close() may now be called on a writer that has already been closed (i.e. conforms to Closeable).
• Assignee: Eric Sammer
• Reporter: Eric Sammer
• Created: 11/Feb/13 06:32
• Updated: 27/Feb/13 04:54
• Resolved: 13/Feb/13 03:28

Description

o.a.avro.file.DataFileWriter implements java.io.Closeable, but violates the contract stated by the interface's close() method javadoc.

Closes this stream and releases any system resources associated
with it. If the stream is already closed then invoking this
method has no effect.

DataFileWriter's close() calls flush() calls sync() which calls assertOpen(). This causes repeated calls to close(), or those on a file that failed to open, to throw an exception which violates the contract. Notably, the following idiom fails (and shouldn't).

import com.google.common.io.Closeables;

// ...

DataFileWriter writer = null;

try {
  writer = new DataFileWriter(...);

  // ...
} finally {
  Closeables.closeQuietly(writer);
}