@ivangreene As I understand it, the question is about using a generated Avro type as the target type of a custom conversion? So whenever you use the logical type "decimal" you would get that generated class as the type of your field?
The target type of the conversion needs to be in the classpath of the Conversion implementation. And the Conversion implementation needs to be in the classpath of the Maven plugin. (See the integration tests for an example of this.) So it would be hard to do with both Avro types being generated at the same time without doing some serious classloading magic in the Maven plugin. However, you could have the project containing the conversion generate its target type from an Avro schema, but that doesn't make much sense to me. It should be pretty straightforward to add tests with new types of schemas in the codegen-test project if you want to try something out. [ Full content available at: https://github.com/apache/avro/pull/329 ] This message was relayed via gitbox.apache.org for [email protected]
