Can you see if there are any errors in the logs/nifi-app.log when this
happens?
From: walter franco <wfranco...@gmail.com> <wfranco...@gmail.com>
Reply: users@nifi.apache.org <users@nifi.apache.org> <users@nifi.apache.org>
Date: August 23, 2021 at 13:17:28
To: users@nifi.apache.org <users@nifi.apache.org> <users@nifi.apache.org>
Subject: Error: will route to failure: Could not parse incoming data
(ConvertRecord)
Hi,
Please your help with this use case
I'm configuring ConvertRecord process, Record Reader JsonTreeReader (default
properties values) and Record Writer AvroRecordSetWriter (default
properties values)
Source message JSON:
{
"data": [
{
"field": null,
"element": null,
"operator": "INTERSECTION",
"values": null,
"children": [
{
"field": null,
"element": null,
"operator": "UNION",
"values": null,
"children": [
{
"field": null,
"element": null,
"operator": "INTERSECTION",
"values": null,
"children": null
},
{
"field": "code",
"element": "item",
"operator": "IGUAL",
"values":
"1040229,3038866,3053614,192813,958192,1445802,1274143,3000209,1554903,1505802,246686,413699,1236441,1513006,1211886,3057720,364104,1661860,364082,1184297,1759087,1671064,1570178,637351,1624603,1657398,1269244,1645180,1495040,1298845,1298846,1278091,1661843,1345281,1476559,1476562,1476563,1476564,1476567,1476570,1588282,1588283,1588284,1588285,1588292,1442335,893507,1606251,1300585,1640078,1606250,1734621,1318655,279891,1788816,1707544,1757195,3017224,1543115,1740934,1740935,1558395,1558398,1174491,1174493,3007533,1231189,1294801,3011056,1622560,1623816,1361640,1361643,1361644,1361645,1361664,1361665,1361666,1371071,1371083,1371101,1371253,1371264,3003983,3004012,3004013,1702758,1741807,1741809,1741810,1769991,1501888,1501889,1503467,3002275,3001177,3001178,1658833,1515369,3018817,1784221,1784222,1784223,478559",
"children": null
}
]
},
{
"field": "ecp",
"element": "item",
"operator": "IGUAL",
"values": "40,30,10,60,50",
"children": null
}
]
}
]
}
And, it generates an error in the ConvertRecord [will route to failure:
Could not parse incoming data]. I think it is because of the use of
multiple children key (sub-level). These messages are of legacy solutions,
so I can't change that origin format. Is it possible to handle this type of
message with this process?
Thanks for your help
Best regards
Franco
