Part of the point of having a framework like metron is that you don’t *need* to know those things to contribute parsers. What you would want to understand are the things at parser scope:
STELLAR, the MessageParser interface The base ‘typed’ parsers ( JSONMap, CSVParser, BasicGrokParser ) and your data. Even the integration testing framework has been done in such a way that you can test with indexing, enrichment etc without having to worry about setting up zookeeper, kafka, storm etc. On May 11, 2017 at 09:38:46, Mark de Rijk ( mark.der...@samarkconsulting.co.uk) wrote: Hi, I really would like to help with parser development. I am reading up on Nifi, Kafka and there are probably other topics I am missing now. As when it comes to Hadoop ecosystem I am pretty much a beginner I will unfortunately need a month to learn the different components. Regards, Mark de Rijk Sent from my iPhone > On 9 May 2017, at 02:23, Otto Fowler <ottobackwa...@gmail.com> wrote: > > There is a readme.md PER parser in 777. > I only stubbed them out however. > > Each parser created by the archetype has one as well. > > What I was hoping to do was to include the parser docs in the package assembly so the UI could load it. > > > > On May 8, 2017 at 19:35:41, Simon Elliston Ball ( si...@simonellistonball.com) wrote: > > Quick thought, and please shoot me down if this has already been thought of, but…. > > Would it be worthwhile if we put some per parser docs into the repo, essentially a README.md per major parser class, which would in theory be picked up by the docbook? We don’t really have much documentation right now on the effect of parserConfig settings for example. > > Similarly, is this something worth considering in the package format, or at least in the archetype proposed by METRON-777 (paging Ottto!) > > Worth the effort? I’m happy to do at least a few of the more recent ones I’ve spent meaningful time with. > > Simon
