Avro合同与枚举的兼容性 [英] Compatibility of Avro contract with enum

问题描述

我有一个现有的Avro模式

I have an existing avro schema

{
"name": "myenum",
"type": {
        "type": "enum",
        "name": "Suit",
        "symbols": ["SPADES", "HEARTS", "DIAMONDS", "CLUBS"]
    },
"default": null
}

我想将null添加为默认值，并将合同更新为以下结果，从而导致向后兼容错误.该如何解决这个问题

I want to add null to be the default and updating the contract to the following result in backward compatibility error. what can be done to solve this issue

{
"name": "myenum",
"type": [ null, {
        "type": "enum",
        "name": "Suit",
        "symbols": ["SPADES", "HEARTS", "DIAMONDS", "CLUBS"]
    }],
"default": null
}

推荐答案

添加的 null 有问题.

即

{
    "name": "myenum",
    "type": [ null, { <- problem
        "type": "enum",
        "name": "Suit",
        "symbols": ["SPADES", "HEARTS", "DIAMONDS", "CLUBS"]
    }],
    "default": null
}

应在引号内: null =>"null" .因此，更新后的定义将如下所示:

It should be within quotes: null => "null". So updated definition will be like:

{
    "name": "myenum",
    "type": [ "null", { <- change
        "type": "enum",
        "name": "Suit",
        "symbols": ["SPADES", "HEARTS", "DIAMONDS", "CLUBS"]
    }],
    "default": null
}

这篇关于Avro合同与枚举的兼容性的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！