ottobackwards commented on issue #3455: NIFI-5900 Add SelectJson processor
URL: https://github.com/apache/nifi/pull/3455#issuecomment-543951918
@arenger hope you are holding out patience wise on this. Hopefully some
traction soon ( although it looks like it will be post release )
ottobackwards commented on issue #3455: NIFI-5900 Add SelectJson processor
URL: https://github.com/apache/nifi/pull/3455#issuecomment-534050870
+1 from me
This is an automated message from the Apache Git Service.
To respond
ottobackwards commented on issue #3455: NIFI-5900 Add SelectJson processor
URL: https://github.com/apache/nifi/pull/3455#issuecomment-533879740
Besides de-conflicting, from my POV, I think that there needs to be some
consensus on which of the approaches makes for sense for the project. I
ottobackwards commented on issue #3455: NIFI-5900 Add SelectJson processor
URL: https://github.com/apache/nifi/pull/3455#issuecomment-494369634
@bbende what would you suggest to move these two PR's forward ( or one of
them rather )? I think that on of them should land, but the decision
ottobackwards commented on issue #3455: NIFI-5900 Add SelectJson processor
URL: https://github.com/apache/nifi/pull/3455#issuecomment-488009910
So, I don't think split record supports a query. Where as split json can
reach into a json structure and find an internal array and split _that_
ottobackwards commented on issue #3455: NIFI-5900 Add SelectJson processor
URL: https://github.com/apache/nifi/pull/3455#issuecomment-487568050
@bbende I am not familiar with the split/partition records. The issues I
*think* in the past would have been not having a schema, and the
