Re: Issue with ValidateRecord processor and Avro map data type

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",

Controllser Service validation

Scenario: We have a custom Controller Service which was deprecated in favor of its replacement (also custom.) The original CS extends the new CS, and contains just a single method: customValidate. This remained intact to log a message saying "Don't use me.. use the new one." When NiFi was

Re: Issue with ValidateRecord processor and Avro map data type

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

Re: Issue with ValidateRecord processor and Avro map data type

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",

Re: Controllser Service validation

There are arguments to be made for continuing to validate components such as Controller Services, Processors, etc.. periodically regardless of whether their properties change or not. That would be based on their environmental interests changing outside their control. However, what you describe

Re: Issue with ValidateRecord processor and Avro map data type

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

Re: Issue with ValidateRecord processor and Avro map data type

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

Re: Issue with ValidateRecord processor and Avro map data type

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]

Issue with ValidateRecord processor and Avro map data type

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:

Nifi very high cpu and memory utilization

Hi, i have a very very big and complex messaging system built in Nifi 1.7.1, the issues are as follows: Using visualvm i got this result Using top i got this result