[AVRO-1247] Fix bug when using custom classloader

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.7.3
• Fix Version/s: 1.7.4
• Component/s: java
• Labels: patch
• Tags: classloader
• Assignee: Doug Cutting
• Reporter: Java Developer
• Created: 10/Feb/13 00:07
• Updated: 27/Feb/13 00:53
• Resolved: 14/Feb/13 21:29

Description

I created a SpecificResponder with a SpecificData which contains my custom classloader (Play Framework's custom classloader actually). However, it's a real pain to do because SpecificResponder.getDatumReader and SpecificResponder.getDatumWriter don't use the SpecificData that I passed in. When creating a new object those two methods should use the SpecificData object that was passed in the constructor.

SpecificResponder.java

  @Override
  protected DatumWriter<Object> getDatumWriter(Schema schema) {
    // It currently uses SpecificData.INSTANCE which makes using a different ClassLoader very difficult
    // return new SpecificDatumWriter<Object>(schema);
    return new SpecificDatumWriter<Object>(schema, data);
  }

  @Override
  protected DatumReader<Object> getDatumReader(Schema actual, Schema expected) {
    // It currently uses SpecificData.INSTANCE which makes using a different ClassLoader very difficult
    // return new SpecificDatumReader<Object>(actual, expected);
    return new SpecificDatumReader<Object>(actual, expected, data);
  }