[
https://issues.apache.org/jira/browse/AVRO-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated AVRO-1847:
------------------------------
Resolution: Fixed
Fix Version/s: 1.8.2
1.9.0
Release Note:
Users of the Java Specific API who have decimal logical types may now opt-in to
having their generated classes use BigDecimal to represent values rather than
the serialized ByteBuffer.
To use this feature programmatically with the SpecificCompiler class, pass true
to the setEnableDecimalLogicalType method.
To use this feature with the specific compiler tool, pass the cli arg
'-bigDecimal'.
To use this feature with the avro maven plugin's code generation, set the
configuration parameter enableDecimalLogicalType to true.
Status: Resolved (was: Patch Available)
> IDL compiler uses ByteBuffer for decimal type even if logical type is
> supported
> --------------------------------------------------------------------------------
>
> Key: AVRO-1847
> URL: https://issues.apache.org/jira/browse/AVRO-1847
> Project: Avro
> Issue Type: Bug
> Components: java
> Affects Versions: 1.8.0
> Reporter: Yibing Shi
> Assignee: Yibing Shi
> Fix For: 1.9.0, 1.8.2
>
> Attachments: AVRO-1847.1.patch, AVRO-1847.2.patch, AVRO-1847.3.patch,
> AVRO-1847.4.patch, AVRO-1847.5.patch, AVRO-1847.6.patch, AVRO-1847.7.patch,
> AVRO-1847.8.patch
>
>
> Version 1.8.0 has added the support of logical types. A conversion class
> (Conversions.DecimalConversion) has also been added for decimal type.
> However, the IDL compiler still uses ByteBuffer for decimal types, which is
> not the same behaviour as data, time or timestamp type (added in AVRO-1684).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
