[AVRO-2401] Initializing decimal fields with fixed fields can cause padding issues in Java

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Component/s: java
• Assignee: Zezeng Wang
• Reporter: Gray
• Created: 20/May/19 16:25
• Updated: 26/Nov/19 08:50

Description

I'm having a hard time figuring out if this a a bug or expected behavior.  If we initialize a decimal field with a fixed logical type that has fewer bytes then the fixed size has, then the bytes get padded on the right with 0s.  This changes their resulting decimal value.  I think they should be padded from the left.  The spec is vague here so I'm not sure if this is a bug or just unexpected outcome.

I've attached my junit test.  The result of the test is:  AssertionError: expected:<660.51> but was:<169090.56>

Issue Links

• links to: GitHub Pull Request #725