Casey, Would things implemented this way be a better way to automate these flows ( built in error handling and checking as standards ) and not just for a user at the terminal?
On September 24, 2016 at 19:02:59, Casey Stella ([email protected]) wrote: Sorry, I meant to ask if anyone had feedback or thoughts. On Sat, Sep 24, 2016 at 18:35 Casey Stella <[email protected]> wrote: > Grok-based parsers are an important part of Metron and Grok is an > extremely adaptable, if complex, language for specifying structure in data. > > > Right now, the flow is generally: > > 1. Get some sample data > 2. Use an online utility to test grok statements > 3. upload grok statement to HDFS > 4. restart parser topology > > Given the demo around managing stellar transformations inside of the REPL, > I began to think that it might be a more coherent and integrated experience > to manage grok inside of the REPL. > > This would involve stellar functions to > > - test grok statements > - read grok statements from HDFS > - push grok statements to HDFS > > I made a few JIRAs to outline it here > <https://issues.apache.org/jira/browse/METRON-454>. >
