That doesn't look like the right way to specify an empty array. This SO example fits about what I'd expect:
https://stackoverflow.com/a/42140165/284538 So it should be default:[0] On Tue, Feb 27, 2018 at 8:56 AM, Mark Payne <[email protected]> wrote: > Juan, > > So the scenario that you laid out in the NIFI-4893 is not one that I've > personally > encountered. What does it mean exactly to have an Avro schema with an > "array" type > that has a value? In the example that you laid out, the field has: > > "type": {"type": "array", "items": "int" }, "default": 0 > > > In this case, what should be the value of this field if it's not > specified? A single-element array with the value of 0? > From looking at the PR that was submitted, it appears to set the > defaultValue to a new (empty) ArrayList. > I would think that maybe it should set defaultValue to > > new Integer[] {0}; > > But I am not certain of the semantics here. > > Thanks > -Mark > > > On Feb 27, 2018, at 7:30 AM, Juan Pablo Gardella < > [email protected]> wrote: > > Hello team, > > I could not fix the issue. I did a patch but it's solves the issue, but I > believe is not the correct solution. Anyone that knows Record Framework can > help me on that? > > Thanks in advance, > Juan > > On Mon, 19 Feb 2018 at 22:33 Juan Pablo Gardella < > [email protected]> wrote: > >> I saw an issue in a test :(. I will continue looking into current >> approach. >> >> On Mon, 19 Feb 2018 at 22:23 Juan Pablo Gardella < >> [email protected]> wrote: >> >>> Hello team, >>> >>> I filed an issue at https://issues.apache.org/jira/browse/NIFI-4893. I >>> discovered using a complex Avro schema. I've isolated the issue and also >>> did a patch. At least, this solve the issue but actually I don't know well >>> the implications on that solution. >>> >>> Please let me know what do you think. I have another issue related to >>> Avro and Record, I will file the issue tomorrow. >>> >>> Thanks, >>> Juan >>> >> >
