Create self-describing Avro for enriched events

[fblundun]

The first version of the Avro will probably have:

• A field containing the version of the schema
• A data field containing:
  • The version of the TSV
  • The TSV

[fblundun]

First draft:

{
    "name": "EnrichedEvent",
    "type": "record",
    "fields": [
        {
            "name": "version",
            "type": "string"
        },
        {
            "name": "columns",
            "type": {
                "type": "array",
                "items": {
                    "name": "column",
                    "type": "string"
                }
            }
        }
    ]
}

Note this isn't yet self-describing.

[alexanderdean]

I like! On 11 Sep 2015 11:18 am, "Fred Blundun" notifications@github.com wrote:

First draft:

{ "name": "EnrichedEvent", "type": "record", "fields": [ { "name": "version", "type": "string" }, { "name": "columns", "type": { "type": "array", "items": { "name": "column", "type": "string" } } } ] }

Note this isn't yet self-describing.

— Reply to this email directly or view it on GitHub https://github.com/snowplow/iglu-central/issues/212#issuecomment-139508768 .

[fblundun]

Actually we should allow the elements of the array to be null, since most of our fields aren't populated at all:

{
    "namespace": "com.snowplowanalytics.avro",
    "name": "EnrichedEvent",
    "type": "record",
    "fields": [
        {
            "name": "version",
            "type": "string"
        },
        {
            "name": "columns",
            "type": {
                "type": "array",
                "items": ["null","string"]
            }
        }
    ]
}

[alexanderdean]

Agree