Change the order in which datum writer is selected
Due to GenericRecord being checked before SpecificRecordBase, GenericDatumWriter was used incorrectly for types that extend SpecificRecordBase. Resolves #3859
This commit is contained in:
committed by
Mahmoud Ben Hassine
parent
4af4b05e33
commit
f4e14ddf66
@@ -1,5 +1,5 @@
|
||||
/*
|
||||
* Copyright 2019 the original author or authors.
|
||||
* Copyright 2019-2021 the original author or authors.
|
||||
*
|
||||
* Licensed under the Apache License, Version 2.0 (the "License");
|
||||
* you may not use this file except in compliance with the License.
|
||||
@@ -155,14 +155,12 @@ public class AvroItemWriter<T> extends AbstractItemStreamItemWriter<T> {
|
||||
}
|
||||
|
||||
private static <T> DatumWriter<T> datumWriterForClass(Class<T> clazz) {
|
||||
if (GenericRecord.class.isAssignableFrom(clazz)) {
|
||||
return new GenericDatumWriter<>();
|
||||
|
||||
}
|
||||
if (SpecificRecordBase.class.isAssignableFrom(clazz)){
|
||||
return new SpecificDatumWriter<>(clazz);
|
||||
}
|
||||
|
||||
if (GenericRecord.class.isAssignableFrom(clazz)) {
|
||||
return new GenericDatumWriter<>();
|
||||
}
|
||||
return new ReflectDatumWriter<>(clazz);
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user