Hi Bryan, This will be very useful feature.
Thanks, Bob Bryan Bende wrote > Bob, > > I think this is slightly different than what you are suggesting, but in > the > next release there is a new AttributesToJson processor makes it very easy > to construct a new json document from values that were extracted using > EvaluateJsonPath. > > Would this makes things a bit easier for sending json to ConvertJsonToSql? > > -Bryan > > On Tue, Dec 1, 2015 at 4:14 PM, Bob ZHao < > bob.zhao.work@ > > wrote: > >> Hello, >> >> I like the idea to support more on tabular data target. But it might take >> a >> long way to go. >> I have a quick enhancement suggestion. >> >> *COnvertJSONToSQL* only support flat JSON structure instead of the >> complicated format -- this make sense. But since we can use >> *EvaluateJsonPath* to filter our the target fields, could we combine them >> together for a new one *PutPropertyToSQL*? This could be very quick >> implementation. >> >> NIFI needn't to worry about the complex of Json, user can use JsonPath >> to >> chop the fields and fragments for customization. >> Then put the result to target table. BTW, please use a trick to save the >> raw >> Json - by pointing to a column. >> >> Thanks, >> Bob >> >> >> >> >> -- >> View this message in context: >> http://apache-nifi-developer-list.39713.n7.nabble.com/PutSQL-feature-enhancement-PutPropertyToSQL-tp5536.html >> Sent from the Apache NiFi Developer List mailing list archive at >> Nabble.com. >> -- View this message in context: http://apache-nifi-developer-list.39713.n7.nabble.com/PutSQL-feature-enhancement-PutPropertyToSQL-tp5536p5540.html Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.
