[
https://issues.apache.org/jira/browse/GORA-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lewis John McGibbney updated GORA-397:
--------------------------------------
Description:
Right now in the GoraCompiler we do not support predefining field types based
on ordering of .avsc as it is passed into the GoraCompiler.
This is supported in the Avro SpecificCompiler meaning that you can write
schemas which inherit fields of custom type based on the compiler reading the
custom type before it is used within the compilation and use of this type in
another schema.
This feature is VERY useful when working with complex schema models and where
you wish to separate out and maintain individual objects rather than explicitly
nest them in large, difficult to maintain schema objects!
was:
Right now in the GoraCompiler we do not support predefining field types based
on ordering of .avsc as it is passed into the GoraCompiler.
This is supported in the Avro SpecificCompiler meaning that you can write
schemas which inherit fields of custom type based on the compiler reading the
custom type before it is used within the compilation and use of this type in
another schema.
This feature is VERY useful when working with scomplex schema models and where
you wish to separate out and maintain individual objects rather than explicitly
nest them in large, difficult to maintain schema objects!
> Support pre-defining types within GoraCompiler
> ----------------------------------------------
>
> Key: GORA-397
> URL: https://issues.apache.org/jira/browse/GORA-397
> Project: Apache Gora
> Issue Type: Improvement
> Components: avro, gora-compiler
> Affects Versions: 0.5
> Reporter: Lewis John McGibbney
> Fix For: 0.8
>
>
> Right now in the GoraCompiler we do not support predefining field types based
> on ordering of .avsc as it is passed into the GoraCompiler.
> This is supported in the Avro SpecificCompiler meaning that you can write
> schemas which inherit fields of custom type based on the compiler reading the
> custom type before it is used within the compilation and use of this type in
> another schema.
> This feature is VERY useful when working with complex schema models and where
> you wish to separate out and maintain individual objects rather than
> explicitly nest them in large, difficult to maintain schema objects!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
