Migrating the ES client, refactoring parser bolt. There are some interface
changes in flight right now that I think would be beneficial to see in the
next release.
On Tue, Oct 16, 2018 at 2:01 PM Nick Allen wrote:
> I am in favor of a release for both.
>
> There are a lot of really useful bug fi
I am in favor of a release for both.
There are a lot of really useful bug fixes, management of pcap through
Ambari, more flexibility for configuring JAAS in Ambari, increased
Elasticsearch performance, the Syslog parser, and the Batch Profiler, among
others. I would be happy with calling it a 0.6.
I agree with a metron-bro-plugin-kafka release of 0.3.0 (0.3 in bro-pkg),
assuming we can get apache/metron-bro-plugin-kafka#2 in. I'm working on
adding travis to the metron-bro-plugin-kafka repo, but I'm not sure when I
will have enough time to finish my work there and wouldn't want to hold up
a
I'd be +1 on going with just the metron-bro-kafka-plugin release. It seems
like it's ready to go, and I think there are a few more things I'd like to
see get into our next Metron release so I'm good with holding off there.
Mike
On Tue, Oct 16, 2018 at 10:26 AM Justin Leet wrote:
> Hi all,
>
> A
I'm still +1 to this approach. Thanks guys!
To Tibor's other point - the management UI is currently a completely
separate service, as I understand it. If there is infrastructure you think
is shareable while still allowing them to be independently deployed, then I
think it would be desirable to mak
Hi all,
As you might recall from a prior discussion about release cadence, we were
interested in initiating release threads near our board reports to see if
we wanted to do releases or not. Additionally, the work is done to do two
separate releases, so our options are releasing both, a single one,
Hi Muhammed,
I think you probably want to start with our parser infrastructure rather
than the DAO's for what you're doing. This series of blog posts gives a use
case driven walkthrough that should help shed some light on things:
Part 1 (start here) -
https://cwiki.apache.org/confluence/display/ME
Thanks, Tamas! The plan you described seems a good approach to me.
Let's wait another day before we create Jira tickets from these steps to
make sure no one else has other concerns.
One more question: how much of these changes could be applicable to the
Management UI?
It would be great plus to see
I'm agreeing with moving forward with Ng Bootstrap. In order to do that, I
think it would be a good start to refactor those components which use the
obsolete jquery based vesrion of bootstrap. Shane has already started it by
refactoring the Modal dialog in the management UI (We also have this
compo
