Thanks Matt, I could make use of the rest api to automate the template sync
work.😀
2017-09-15 1:00 GMT+08:00 Matt Gilman :
> Ben,
>
> In the 0.x baseline, the templates were stored in the templates directory
> that you're referring to. Starting in the 1.x baseline, the templates were
> migrated t
Currently working on one of the feature but while running full build (mvn
-Pcontrib-check clean install) at NIFI root, as suggested in Contribution
Guide, the build is failing in other module in Test scope.
I am certain it's not in my module as it's coming in master branch as well. And
I am hitt
Sorry if you received this mail twice.
Currently I'm working on the feature but while running full build (mvn
-Pcontrib-check clean install) at NIFI root, as suggested in Contribution
Guide, the build is failing in other module in Test scope.
I am certain it’s not in my module as it’s coming in
Is there an easy way to "flatten" arbitrary JSON within NiFi?
For input data like that shown below from Yahoo [1]
{
"query": {
"count": 1,
"created": "2017-09-15T11:20:26Z",
"lang": "en-US",
"results": {
"channel": {
"item": {
"condition": {
"
Nick,
I do believe that there's a way to do what you're asking with Jolt, without
knowing any kind of schema.
That said, Jolt can get complex pretty quickly and I don't know it well :)
Personally, I have no problem with having a
FlattenRecord processor. I guess the question here, though, is are
Mark,
I'm definitely for making the processor as generic as possible. I don't
mind chaining together a few simple processors to get a job done (such as
convert JSON to Avro > infer schema > flatten records)... I just don't want
steps get super complex... and the Jolt Transform processor does seem
+1 for adding a FlattenRecord processor. I can think of a few scenarios in
which it would be quite useful, and it would be convenient if it could be
accomplished without JOLT.
Thanks,
Kevin
On 9/15/17, 09:16, "Nicholas Hughes" wrote:
Mark,
I'm definitely for making the processor