[AVRO-1847] IDL compiler should use BigDecimal to represent decimal logical type. - ASF JIRA

Voters

Watch issue

Watchers

Create sub-task

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: New Feature
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: 1.8.0
Fix Version/s: 1.9.0, 1.8.2
Component/s: java
Labels:
None

Release Note:

Hide
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.

Show
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.

Description

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~~).