Re: Metron Release 0.6.1 and/or Plugin release 0.3.0?

2018-12-05 Thread zeo...@gmail.com
I agree, I would suggest moving forward with cutting an apache/metron RC. Jon On Wed, Dec 5, 2018 at 3:45 PM Nick Allen wrote: > I would prefer to just go ahead with the release and not wait on an > intermittent, integration test related JIRAs. Just wanting to see if there > is support for

Re: Metron Release 0.6.1 and/or Plugin release 0.3.0?

2018-12-05 Thread Nick Allen
I would prefer to just go ahead with the release and not wait on an intermittent, integration test related JIRAs. Just wanting to see if there is support for getting a RC out sooner rather than later. On Tue, Dec 4, 2018 at 4:06 PM zeo...@gmail.com wrote: > I agree that we should move forward

Re: [DISCUSS] Recurrent Large Indexing Error Messages

2018-12-05 Thread Otto Fowler
Why not have a second indexing topology configured just for errors? We can load the same code with two different configurations in two topologies. On December 5, 2018 at 03:55:59, Ali Nazemian (alinazem...@gmail.com) wrote: I think if you look at the indexing error management, it is pretty

Re: [DISCUSS] Recurrent Large Indexing Error Messages

2018-12-05 Thread Ali Nazemian
I think if you look at the indexing error management, it is pretty much similar to parser and enrichment error use cases. It is even more common to expect something ended up in error topics. I think a wider independent job can be used to take care of error management. It can be decided to add a