Hi @jerry_pylarinos and @mburgess  I am seeing weird behavior in the same scenario but the only difference is my spec has expression language inside Jspec and it never resolved after pulling from the cache and passing as an attribute to jolttransform. Is that a bug?   like if you jspec.json has [ { "operation": "modify-overwrite-beta", "spec": { "id": "${UUID()}" } } ]   and your generate flow file has  { "id" : "anyname" }   You result looks like this { "id":"${UUID()}" }   How to evaluate expression langauge here? ... View more

Hi @dyadav1   Thanks for pointing out the direction for Kafka topic but I need little more help to determine the strategy, as I mentioned if every topic is putting 100 different types of command and I need to transform each type of command into new type (assuming Jolt transformation and have jolt spec for 100 different command types), how do I store those spec and make generalize flow so that new command types get added I just need to update Spec and flow didn;t require any changes. In more terms need to dynamically figure out which command type coming in the flow file and transform it based on spec, now I feel I need to use lookup and if I store all spec in database but then for each transformation I need to do database trip which I want to avoid. ... View more