I believe it's a bug too. Thank you Matt for opening the issue !
On Wed, Oct 10, 2018 at 5:15 PM Matt Burgess wrote:
> Maxime,
>
> I believe this is a bug, specifically at [1]. It should support
> MapRecord entries as well. I have written NIFI-5678 [2] to address
> this. The workaround is the
Maxime,
I believe this is a bug, specifically at [1]. It should support
MapRecord entries as well. I have written NIFI-5678 [2] to address
this. The workaround is the one you and Bryan mentioned, using a
record instead of a map.
Regards,
Matt
[1]
Yes I made it worked with record type as well but I can't use a record
because my field names are dynamic.
In many JSON we use collections of keys that will be named at runtime. I
thought the map data type of Avro was specially designed for it
Any other ideas ?
On Wed, Oct 10, 2018 at
I was able to make it work using a nested record instead of a map
{
"type": "record",
"name": "example",
"fields" : [
{
"name": "field1",
"type": {
"name" : "field1",
"type" : "record",
"fields" : [
{ "name": "toto",
Sure, here is the schema :
{
"name" : "test",
"type" : "record",
"fields" : [ {
"name" : "field1",
"type" : {
"type" : "map",
"values" : "string"
}
} ]
}
And here is the JSON message :
[{
"field1": {
"toto" : "v1",
Hello,
The screenshots did not come through, maybe just paste the schema and JSON
as text in the email.
Thanks.
On Wed, Oct 10, 2018 at 6:57 AM Maxime Jattiot
wrote:
> Hello everyone,
>
> I am having hard time to validate a simple JSON message with an Avro
> schema. My schema works with
Hello everyone,
I am having hard time to validate a simple JSON message with an Avro
schema. My schema works with avro-tools but doesn't with ValidateRecord
processor. I wish you could help me.
- I am having the following debug log within Nifi :
Record #1 is invalid due to:
