AVRO-3218: Fix parsing of logicalType = decimal

[vegraux]

Make sure you have checked all steps below.

Jira

• My PR addresses the following AVRO-3218 issue

Tests

• My PR adds to the following unit tests: lang/py/avro/test/test_schema.TestMisc.test_decimal_valid_type:

Commits

• My commits all reference Jira issues in their subject lines. In addition, my commits follow the guidelines from "How to write a good git commit message":
  1. Subject is separated from body by a blank line
  2. Subject is limited to 50 characters (not including Jira issue reference)
  3. Subject does not end with a period
  4. Subject uses the imperative mood ("add", not "adding")
  5. Body wraps at 72 characters
  6. Body explains "what" and "why", not "how"

Documentation

• In case of new functionality, my PR adds documentation that describes how to use it.
  • All the public functions and the classes in the PR contain Javadoc that explain what it does

[vegraux]

@martin-g I fixed the lint-issue and amended to the same commit

[vegraux]

@martin-g How is the timeline for merging?

[martin-g]

I am not a member of Apache Avro team. I am just a contributor who helps in areas I have some knowledge.
Apache Avro 1.11.0 rc1 is being voted at the moment at dev@.
So this PR will have to wait for 1.11.1/1.12.0.

[vegraux]

@RyanSkraba Is there a place I can check to see what is planned to be included in future releases? Would really appreciate to get this in 1.11.1, it is a really annoying bug

[martin-g]

The way to schedule something for a specific release is to set the "Fix Version" in the JIRA ticket.
This way the ticket will be reviewed before the release. If everything is clear and the PR is approved then it will be resolved. Otherwise the Fix Version will be edited.
In both cases the release manager will take your ticket into account when the release time comes.
Depending on how many tickets are fixed and what kind of changes are applied with them it might be versioned as 1.11.1 or 1.12.0.

[kojiromike]

I don't think we have a policy that says that merging a PR has to wait for a specific release. The actual release process uses different branches. So I'm happy to merge this now, and then if the ticket says this bugfix needs to go into 1.11.1 then it can.

[cccs-eric]

@martin-g I just ran into this issue and wanted to contribute a fix when I discovered that master already contains a fix! Would it be possible to know when 1.11.1 will be released? This is a blocker for me....

[martin-g]

There is a mail thread about this at dev@ mailing list.
I hope it will be released soon!

[vegraux]

@RyanSkraba When is the next release (1.11.1) planned? I must manually build avro with the bugfix, and push to my company's artifactory to get around this. It often causes dependency problems

[vegraux]

There is a mail thread about this at dev@ mailing list. I hope it will be released soon!

Do you have an update on the release @martin-g?

[martin-g]

https://lists.apache.org/thread/jbxzoq091ozy7gp7vb93m8ztlgjct7fq