[GitHub] metron issue #914: METRON-1397 Support for JSON Path and complex documents i...
Github user cestella commented on the issue: https://github.com/apache/metron/pull/914 I love this, sorry I didn't review it sooner @ottobackwards +1 by inspection. This is great. ---
[GitHub] metron issue #914: METRON-1397 Support for JSON Path and complex documents i...
Github user simonellistonball commented on the issue: https://github.com/apache/metron/pull/914 My bad: the dependencies file is updated, but not the NOTICES. ---
[GitHub] metron issue #914: METRON-1397 Support for JSON Path and complex documents i...
Github user simonellistonball commented on the issue: https://github.com/apache/metron/pull/914 And in fairness to you, we don't do the NOTICES properly for anything else either I see. That's probably a separate scope. ---
[GitHub] metron issue #914: METRON-1397 Support for JSON Path and complex documents i...
Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/914 Um, it is updated. ---
[GitHub] metron issue #914: METRON-1397 Support for JSON Path and complex documents i...
Github user simonellistonball commented on the issue: https://github.com/apache/metron/pull/914 And in more topical an relevant points... we're introducing a net new dependency here... Do we need to also update the NOTICES file (and the dependencies_with_url.csv list)? ---
[GitHub] metron issue #914: METRON-1397 Support for JSON Path and complex documents i...
Github user simonellistonball commented on the issue: https://github.com/apache/metron/pull/914 @ottobackwards Really want that myth to be a reality... as soon as we can get the config overwrite problem solved... but this really isn't the ticket to discuss that on :) I'm kinda keen on this parser looking at things like CloudTrail logs and such like which appear with merged JSON right now. The other thing that I think this would link up to is the idea that's been floating around about chaining parsers. This parser could well be a split parser, which then routes to other parsers with different transformations for example depending on the message, but again, that's deep future and should probably be on a discuss thread about parser chaining. ---
[GitHub] metron issue #914: METRON-1397 Support for JSON Path and complex documents i...
Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/914 Just a note on parser docs, part of the mythical 777 is support for per parser readme, that would be nice here. ---
[GitHub] metron issue #914: METRON-1397 Support for JSON Path and complex documents i...
Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/914 yeah, you said in the docs, will do ---
[GitHub] metron issue #914: METRON-1397 Support for JSON Path and complex documents i...
Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/914 http://goessner.net/articles/JsonPath/ https://github.com/json-path/JsonPath http://jsonpath.herokuapp.com https://docs.spring.io/spring-boot/docs/current/reference/html/boot-features-testing.html ---
[GitHub] metron issue #914: METRON-1397 Support for JSON Path and complex documents i...
Github user mmiklavc commented on the issue: https://github.com/apache/metron/pull/914 This seems cool. Can you provide some guidance via some examples or just a link to what's possible syntax/query-wise with JSON path queries in the docs for this? ---
