[NIFI-5138] JSON Record Readers providing wrong schema to sub-records when there is a CHOICE of multiple RECORD types

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.7.0
• Component/s: Extensions
• Assignee: Mark Payne
• Reporter: Mark Payne
• Created: 02/May/18 12:45
• Updated: 09/May/18 16:39
• Resolved: 09/May/18 16:39

Description

When the JSON Record Reader is used, if the schema provides a CHOICE of two different RECORD types for a sub-record, then the sub-record's schema ends up being an empty schema. This results in RecordPath's not properly evaluating. For example, with the schema below:

{
  "name": "top", "namespace": "nifi",
  "type": "record",
  "fields": [
    { "name": "id", "type": "string" },
    { "name": "child", "type": [{
         "name": "first", "type": "record",
         "fields": [{ "name": "name", "type": "string" }]
       }, {
         "name": "second", "type": "record",
         "fields": [{ "name": "id", "type": "string" }]
       }]
     }
  ]
}

 

If I then have the following JSON:

{
  "id": "1234",
  "child": {
      "id": "4321"
  }
}

The result is that the record returned has the correct schema. However, if I then call record.getValue("child") I am returned a Record object that has no schema.

This results in the RecordPath "/child/id" returning a null value.

 

Issue Links

• links to: GitHub Pull Request #2670