Bump github.com/linkedin/goavro/v2 from 2.10.0 to 2.12.0

[dependabot]

Bumps github.com/linkedin/goavro/v2 from 2.10.0 to 2.12.0.

Release notes

Sourced from github.com/linkedin/goavro/v2's releases.

Release to fix Version Number

The version number should be the full v2.12.0 to be fully semver compatible. There's no new content in this release. Its just the fix to the version number.

Thanks

Here are the release notes copied from v2.12:

This release includes full support for sending regular internet JSON into avro and getting regular JSON back out again, and a large number of cleanup and fixing. Many thanks to the help from the community!

• A large number of cleaning up and fixes from @​mihaitodor
• Full two-way json serialization support for regular internet json
• OCF reader and writer from @​kishaningithub

About JSON to Avro and Avro to JSON

Regular internet json is wild and can have various values for a particular field, such as a "human" field having a value of null of maybe a string containing a name, or even a struct containing details about the "human". To handle accepting JSON of such a form, the previous release provided a one-way JSON encoder, where an avro union is required to be defined, in order to accept the possible types that we will can expect. This functionality was provided in the previous release, but the previous release did not take avro encoded data from within the avro ecosystem and produce regular internet JSON. Instead it produced the style of avro-json described in the avro-spec. This release provides the full two-way support, so that we can take regular internet JSON into the avro ecosystem, and we can send it back out into the internet's standard json ecosystem.

There are many examples in union_test.go where the production of standard JSON is done via the test utility function testNativeToTextualJSONPass.

Also much gratitude to @​karrick for his work on this project and his ongoing interest and support. Though he did not contribute directly to this release, I still wanted to thank him here.

Custom Logical Types, Enums, Standard JSON

This release contains 3 new capabilities and a fix for canonical representation for enums

• Allow decimal logical type of precision 1
• Added support for custom logical types
• Enum should be managed like records, parent namespace should be used to generate canonical form
• Added nativeFromTextual to support standard json
• Added avro roundtrip debugging tool

Support for Ingestion of Common JSON

There is an increasing demand to ingesting common JSON into the avro-encoded systems.

This release adds support for accepting common JSON , so we can take JSON from regular (non-avro-enabled) applications and encode it into avro per a schema in the expected way. This was a problem because union-types were expected to be of a form that satisfies the avro json encoding spec:

avro spec: ["null", "string"] common json: null, or "some string" avro json encoded: null and {"string": "some string"}

Example code, and tests are included in union_test.go

Commits

• 9a47646 Merge pull request #256 from mihaitodor/fix-lint-action
• 39f6bc3 Fix golangci-lint action
• 89f9e29 Merge pull request #229 from kishaningithub/patch-1
• 48fab01 Merge pull request #245 from mihaitodor/enable-linters
• be79bb9 Merge branch 'master' into enable-linters
• 442327d Merge pull request #249 from xmcqueen/master
• 19f5f16 added comments and renamed per comments
• 326cef1 put in some better testing machinery using a list of test data and a loop ove...
• 08e0e48 added some testing tools and fixed an intermittent failure in the two way jso...
• 441afb4 added support for full two-way json encoding/decoding for standard json #247
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)