You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@avro.apache.org by "Martin Tzvetanov Grigorov (Jira)" <ji...@apache.org> on 2023/06/15 06:55:00 UTC

[jira] [Resolved] (AVRO-3782) [Rust] Incorrect decimal resolving

     [ https://issues.apache.org/jira/browse/AVRO-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Tzvetanov Grigorov resolved AVRO-3782.
---------------------------------------------
    Fix Version/s: 1.12.0
                   1.11.2
         Assignee: Martin Tzvetanov Grigorov
       Resolution: Fixed

> [Rust] Incorrect decimal resolving
> ----------------------------------
>
>                 Key: AVRO-3782
>                 URL: https://issues.apache.org/jira/browse/AVRO-3782
>             Project: Apache Avro
>          Issue Type: Bug
>          Components: rust
>            Reporter: Fedor Telnov
>            Assignee: Martin Tzvetanov Grigorov
>            Priority: Major
>             Fix For: 1.12.0, 1.11.2
>
>
> Currently decimal schema provides incorrect resolving checks when working with decimal values, transformed from BigInt bytes(signed big endian form).
> Currently algorithm of resolving checks for decimal validates that their max precision is less then the precision stated in the schema. It calculates "max" precision by applying formulae, stated in the avro specs(see section for Decimals). But it should not do this in such a case - cuz the max precision of input decimal value is, well, amount of digits in that input value.
> To see what am I talking about, try running a test in the supplied PR.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)