Sounds to me that we should close METRON-370 as non-discrepant. If we want a feature later on to be able to replay enrichments we should add a Jira on that instead. I don't see why you would do this, though. If the enrichment fails you want to pass the message through unenriched. Otherwise if you keep replaying you will backup your ingest pipeline.
02.11.2016, 15:05, "Michael Miklavcic" <[email protected]>: > Hi Jon, I have commented on 370 - > https://issues.apache.org/jira/browse/METRON-370 > > Best, > Mike > > On Wed, Nov 2, 2016 at 3:11 PM, [email protected] <[email protected]> wrote: > >> I personally would like to see the following things done before things >> leave BETA: >> (1) Address data integrity concerns (Specifically thinking of METRON-370, >> METRON-517) >> (2) Make cluster tuning easier and more consistent (METRON-485, METRON-470, >> and the "[DISCUSS] moving parsers back to flux" which I can't find a JIRA >> for). >> >> I would also want to see the upgrade path (as opposed to rebuild) be more >> thoroughly and regularly tested once things leave BETA. From my >> perspective I think the project is very close but not yet ready. >> >> Jon >> >> On Wed, Nov 2, 2016 at 4:44 PM Casey Stella <[email protected]> wrote: >> >> Hello Everyone, >> >> Now that the discussion around the next release has started, it has been >> proposed and I think it's a good time to discuss what to name this next >> release. Before, we have adopted the BETA suffix. I think it might be >> time to drop it and call the next release 0.2.2 >> >> Thoughts? >> >> Best, >> >> Casey >> >> -- >> >> Jon ------------------- Thank you, James Sirota PPMC- Apache Metron (Incubating) jsirota AT apache DOT org
