Avro Support(4.3)

This page describes the Avro support for Ultra Format Definition Language (UFDL). This functionality enables you to compile Avro definitions, and to encode data into, and from the Avro format. A schema in Avro is represented in JSON. You can implement non-protocol data issues in an Analysis agent.

Note!

It is also possible to encode/decode Avro messages using schema retrieved from an external schema registry. See Decoder/Encoder(4.3) for more information.

Overview

Avro parsing in UFDL is managed by applying the avro_block construct.

avro_block { <avro json schema> };

The output from an Avro encoder represents a single Avro record, not a complete Avro data file. To de-serialize these records using a third party tool, add the correct Avro header to the records based on the description of Avro provided in the link below.

The full description of the Avro language can be found at: https://avro.apache.org/docs/current/spec.html.

The Avro Types

The Avro JSON schema can be defined with any of the following types:

Note!

There are limitations to the implementation of the following elements. See the section Limitations below for further information.

Primitive Type

Notes

Primitive Type

Notes

null

Implemented as type byte

boolean

Value must be true or false.

int

32-bit signed

long

64-bit signed

float

Single precision (32-bit) IEEE 754 floating-point number

double

Double precision (64-bit) IEEE 754 floating-point number

bytes

Sequence of 8-bit unsigned bytes

string

Unicode character sequence

Complex Type

Notes

Complex Type

Notes

record

Supports the attributes: name, namespace, doc (optional), aliases (optional), fields.

The fields attribute is an array of listing fields and supports the attributes: name, doc (optional), type, default, order (optional), aliases (optional).

enum

Supports the attributes: name, namespace, doc (optional), aliases (optional), symbols.

array

Supports the attribute: items

map

Supports the attribute: values

union

Implemented as a record with all types set to optional. If two values are set, both are encoded. If no values are set, none are encoded.

To specify a union value, you must use udrCreate.

fixed

Supports the attributes: name, namespace, aliases (optional), size

Note!

Use the doc attribute to add a comment.

Limitations

The following limitations apply for the Avro support in Usage Engine:

  • Line and Column are not fully implemented.

  • No string values are permitted in APL for the enum type.

  • Encoding the Avro object container file is not supported.

  • aliases are not fully supported.

  • default is not fully supported.

  • Cross-references to other Ultra definitions are not supported.

  • array of arrays is not correctly implemented. For example, array of array of x is implemented with array of y, where y is a record with one value field. This value field is an array of x.

  • map of x is implemented via an array of y, where y is a record with two fields: key and value, where value is x.

Avro Format Example

To encode an Arvo data file, a format definition is included in the Ultra avro_block block in the Ultra format.