If you knew the schema of the incoming content, I believe you can use schema aliases in conjunction with ConvertRecord, but since you mention field names are unknown, I'm guessing you won't know the schema(s) either 🙂 You can do this with the JoltTransformJSON processor, although I don't think it supports arbitrary numbers of periods as its matching operator is as non-greedy as possible. Here is a spec that works for 1-3 periods: [
{
"operation": "shift",
"spec": {
"*.*.*.*": "&(0,1)_&(0,2)_&(0,3)_&(0,4)",
"*.*.*": "&(0,1)_&(0,2)_&(0,3)",
"*.*": "&(0,1)_&(0,2)",
"*": "&"
}
}
] Note you could continue this pattern for any discrete number of periods. Also note that the above spec works for "flat" JSON files. For nested fields you'd have to go "one level deeper" and apply the same pattern, here's a spec that works for 1-3 periods, 1-2 fields deep: [
{
"operation": "shift",
"spec": {
"*.*.*.*": "&(0,1)_&(0,2)_&(0,3)_&(0,4)",
"*.*.*": "&(0,1)_&(0,2)_&(0,3)",
"*.*": "&(0,1)_&(0,2)",
"*": {
"*.*.*.*": "&(0,1)_&(0,2)_&(0,3)_&(0,4)",
"*.*.*": "&(0,1)_&(0,2)_&(0,3)",
"*.*": "&1.&(0,1)_&(0,2)",
"*": "&"
}
}
}
] If the incoming JSON is truly "wild west", you could use Groovy in an ExecuteScript processor along with a JsonSlurper (and JsonOutput) to change the keys at arbitrary depths with arbitrary numbers of periods.
... View more
