[ANNOUNCE] - Apache Metron Slack channel

The Metron community has a Slack channel available for communication (similar to the existing IRC channel, only on Slack). To join: 1. Go to slack.com. 2. For organization/group, you'll enter "the-asf" 3. Use your Apache email for your login 4. Click "Channels" and look for #metron

Re: [ANNOUNCE] - Apache Metron Slack channel

+ Metron user list On Wed, Aug 15, 2018 at 10:38 AM Michael Miklavcic < michael.miklav...@gmail.com> wrote: > Turns out we are able to invite folks on an ad-hoc basis. See instructions > here - > https://cwiki.apache.org/confluence/display/METRON/Community+Resources > > &

Re: [DISCUSS] Release cadence

I'm also a fan of the 2-3 month time frame for releases. And I agree it fits nicely with our board report. That said, I think we should minimally kick off a DISCUSS at least every 2 months per the recommendations above. If it's warranted, great. If not, then we bring it up at a stated later time

Re: [DISCUSS] Release cadence

Works for me, that would be great. On Wed, Aug 15, 2018 at 12:22 PM Casey Stella wrote: > If you like, I can volunteer to kick off a discuss thread when I submit the > board report. > > On Wed, Aug 15, 2018 at 2:21 PM Michael Miklavcic < > michael.miklav...@gmail.com>

Re: [DISCUSS] Metron Release 0.6.0?

+1 here as well to the proposed releases. On Wed, Aug 15, 2018 at 11:06 AM Casey Stella wrote: > +1 to both releases, this is plenty for an 0.6.0 and a 0.2.0 > > On Wed, Aug 15, 2018 at 11:04 AM Justin Leet > wrote: > > > I just sent a thread about release cadence. Jon, I'd recommend starting

Re: Slack Channel

Invite sent On Wed, Aug 15, 2018 at 10:57 AM Simon Elliston Ball < si...@simonellistonball.com> wrote: > Hello dev team, may I please join your slack channel :) >

Re: [DISCUSS] Pcap query branch completion

I'm +1, thanks for adding that fix, Ryan. (Note, for purposes of vote, I was a contributor in the feature branch). Mike On Thu, Aug 16, 2018, 4:17 PM Ryan Merriman wrote: > We discovered a bug in our testing and felt it should be fixed before we > merge. There is a PR up for review that

Re: package.lock changes during build?

Somewhere along the line the dependencies appear to have changed, but the file never got checked in. I don't like that this part of our build also seems to be non-deterministic. If I build metron 0.4.x today, for instance, what will I get? If the answer is "who knows?" that's unacceptable, imo.

Re: package.lock changes during build?

there's a dependency that is not version locked (i.e. the most recent > > version of dependency x moved from y to z). > > > > On Sat, Aug 25, 2018 at 11:52 AM Michael Miklavcic < > > michael.miklav...@gmail.com> wrote: > > > > > Somewhere along the line the d

Re: [DISCUSS] Getting to a 1.0 release

Apologies for any spelling mishaps as I'm writing from my phone. I'm for improving our docs. I'd like to see us guide our various profiles of user towards the specific documentation for the abstraction levels they'll be most interested in working from. I think we should have platform docs about

Re: [DISCUSS] Feature branches post-merge

gt; wrote: > > > > > I would drop them. > > > I’ve already clean up FB’s around dead things. > > > > > > > > > > > > On September 6, 2018 at 13:42:55, Michael Miklavcic ( > > > michael.miklav...@gmail.com) wrote: > > > &

Re: [DISCUSS] Split apart releases for core Metron and the Bro plugin

+1 to deferring for this release and having the separation like NiFi. Since we're bootstrapping from their process, what are they doing? I would assume we'd want some sort of vote for the plugin version change as well. On Fri, Sep 7, 2018 at 10:15 AM Nick Allen wrote: > +1 for complete

Re: [DISCUSS] Metron Release 0.6.0?

correct instructions when > merging > > > PR > > > > > into > > > > > > > >> > feature branch (nickwallen) closes apache/metron#1074 > > > > > > > >> > 3 months ago METRON-1630 Add threat.triage.score.field to >

Re: [GitHub] metron issue #1188: METRON-1769: Script creation of a release candidate

Yeah, the Angular upgrade was the other bit that came to mind. Shane's PR for the Angular upgrade has the necessary +1's, but @nickwallen you had requested we hold off on that for this release (which I completely agree with). https://github.com/apache/metron/pull/1096 On Fri, Sep 7, 2018 at 10:24

[DISCUSS] Feature branches post-merge

What are we doing with feature branches once they're complete and merged into master? Is our expectation that we'll keep feature branches in perpetuity, or should we plan to do some house cleaning once they've been merged? I did a quick check of NiFi and Kafka and don't see much by way of feature

Re: [GitHub] metron issue #1188: METRON-1769: Script creation of a release candidate

you need to go through github's UI. > > On Fri, Sep 7, 2018 at 1:34 PM Michael Miklavcic < > michael.miklav...@gmail.com> wrote: > > > Yeah, the Angular upgrade was the other bit that came to mind. Shane's PR > > for the Angular upgrade has the necessary +1's, but @nickw

Re: [DISCUSS] Internal Metron fields

Can you elaborate on what you mean by "convert to internal?" From your description, it looks like the challenge is from our violations of DRY when it comes to constants referencing those keys, which would be eliminated by refactoring. On Fri, Sep 7, 2018, 3:50 PM Ryan Merriman wrote: > I

Re: [DISCUSS] Upgrading Solr

I'm +1 on feature branch and user@ announcement as well. On Thu, Jan 18, 2018 at 12:46 PM, Casey Stella wrote: > +1 to both the feature branch and user@ announcement. > > On Thu, Jan 18, 2018 at 2:45 PM, Otto Fowler > wrote: > > > +1 to the feature

Re: Master is failed in Travis

Yeah, this seems to be breaking in every build at this point. I am going to look into it tomorrow. On Mon, Jan 22, 2018 at 8:29 AM, Nick Allen wrote: > I had copied the wrong text into the bug. I fixed that. > > On Mon, Jan 22, 2018 at 10:22 AM, Casey Stella

Re: Master is failed in Travis

pm. I know Yarn (javascript yarn, not hadoop) has been mentioned before, but I think npm may have some features now as well. Cheers, Mike On Tue, Jan 23, 2018 at 2:45 PM, Michael Miklavcic < michael.miklav...@gmail.com> wrote: > Yeah, this seems to be breaking in every build at thi

[DISCUSS] Metron debug info tool

Hey guys, I wanted to bring attention to a tool I created for gathering cluster details for debugging purposes. There are a number of locations that properties get materialized, e.g. from Ambari -> properties file -> flux -> Storm, which means a lot of hunting to guarantee that the changes you've

Re: [DISCUSS] Metron debug info tool

, > and even build in an export if we wanted to. Would make it a lot easier > for end users to be able to get a quick view into what's going on, and > could let us build in some slightly better filtering and search > capabilities. > > > > On Wed, Apr 11, 2018 at 12:10 PM,

Re: [DISCUSS] Metron debug info tool

sier > > for end users to be able to get a quick view into what's going on, and > > could let us build in some slightly better filtering and search > > capabilities. > > > > > > > > On Wed, Apr 11, 2018 at 12:10 PM, Michael Miklavcic < > > michael.mikla

Re: [DISCUSS] Inactive PRs

I'm for cleaning up the outstanding inactive PR's and putting this in the dev guidelines. I would actually like to push for a time that is less than 6 weeks. Why not 4? We don't risk much - a submitter can always reopen a closed PR, and the history is maintained. Closed PR's don't disappear afaik

[DISCUSS] Metron RPM spec changelog

We discovered yesterday while reviewing a PR that the RPM changelog hasn't been maintained since 9/25/17. There are 7 changes to that file that have not been logged in the changelog itself. The question is if we want to keep maintaining the changelog and, if so, should we patch the existing log

Re: [DISCUSS] Metron RPM spec changelog

to see the changelog only include the release entries, > rather than individual entries per dev. We keep the spec file in source > control to determine the individual changes between releases. I'm happy to > have my mind changed, though. > > On Wed, Apr 18, 2018 at 9:47 AM Michael Miklavcic

Re: [VOTE] Development Guidelines Addendum on Inactive Pull Requests

+1 On Fri, Apr 20, 2018 at 12:54 PM, Casey Stella wrote: > +1 > > On Fri, Apr 20, 2018 at 11:17 AM David Lyle wrote: > > > +1 sounds good to me. > > > > -D... > > > > > > On Fri, Apr 20, 2018 at 11:09 AM, zeo...@gmail.com > > wrote:

Re: [DISCUSS] Knox SSO feature branch review and features

> >> doing things, or we want to use a framework other than Spring for this, > >> then maybe we could change to that, but the route chosen here is > definitely > >> the easy path in the context of the decision made to use Spring in > metron > >> rest, an

Re: [DISCUSS] Knox SSO feature branch review and features

hrough as-is. > > On a side-note, it feels a bit weird that we're narrowing to a bundled > proxy, rather than having that be a pluggable thing. I'm not super > knowledgeable in this space, so I apologize > in advance if this is naive, but isn't this a pluggable, external component

Re: [DISCUSS] Switching to a better alternative of Pikaday.js

to > > >> > decrease the size of the production javascript bundle. I could > achieve > > >> 15% > > >> > loss in the final bundle size which is admittedly not a game changer > > but > > >> > still. Not to mention if we want to heavily

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

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, > >

Re: [DISCUSS] Switching to a better alternative of Pikaday.js

> > date/time picker component based on Ng bootstrap and then we can get rid > of > > Pikaday. > > Once Pikaday is completely eliminated from the system, we can be sure > that > > the PR about eliminating moment.js is ready to go. > > > > Cheers, > >

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

ding that you would like to see in the release? > > On Tue, Oct 16, 2018, 12:21 PM Michael Miklavcic < > michael.miklav...@gmail.com> wrote: > > > 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

Re: [DISCUSS] Slack Channel Use

/1aa85bc13d41e04a1f85c3100c2b803abe35d79b54062bbeaab83ace@%3Cdev.metron.apache.org%3E How very Inception. On Mon, Oct 22, 2018 at 1:32 PM Michael Miklavcic < michael.miklav...@gmail.com> wrote: > I just want to point out that we currently have 32 members in the Metron > Slack channel which I personally think is a great sign. This

Re: Invite to Slack Channel

Muhammed Irshad > wrote: > > > >> Some one get me also the slack channel link ? > >> Thanks, > >> Muhammed Irshad > >> Q*Burst* > >> www.qburst.com > >> > >> > >> On Wed, Oct 17, 2018 at 7:33 PM Michael Mikla

Re: Invite to Slack Channel

:06, Tamás Fodor (ftamas.m...@gmail.com) > wrote: > > > > Hello, > > > > Michael, can you add me as well? > > > > Thank you in advance! > > > > Tamas > > > > On Wed, Oct 3, 2018 at 4:27 PM Michael Miklavcic < > > michael.miklav...@gm

Re: HBaseDao and IndexDao abstraction

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) -

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

sing. > > On Tue, Oct 16, 2018 at 4:42 PM Michael Miklavcic < > michael.miklav...@gmail.com> wrote: > > > 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 > t

Re: metron-elasticsearch integration tests failing after merging in master

That's a new one on me. Does this run locally for you? Failed tests: ElasticsearchUpdateIntegrationTest>UpdateIntegrationTest.test:132 Data store is not updated!. Actual: 0 On Wed, Oct 24, 2018 at 10:10 AM Otto Fowler wrote: > https://travis-ci.org/ottobackwards/metron/jobs/445723343 >

Re: [DISCUSS] Slack Channel Use

> > indexed > > > > > by the major search engines? I have never used a search engine and > > > > > uncovered the answer to my problem in a Slack archive. > > > > > > > > > > On Mon, Oct 22, 2018 at 5:05 PM Otto Fowler < >

Re: [DISCUSS] Migrate from Protractor to Cypress

to Cypress as a next > step! > > Thanks, > Tibor > > On Thu, Sep 27, 2018 at 9:23 AM Tibor Meller > wrote: > > > Great Guys! Thanks for the feedback. I'll move forward as discussed. > > > > Thx > > > > On Wed, Sep 26, 2018 at 11:44 PM Michae

Re: [DISCUSS] Deprecate split-join enrichment topology in favor of unified enrichment topology

; > > > > > > > On Thu, Nov 1, 2018, 6:27 PM Justin Leet < > justinjl...@gmail.com> > > wrote: > > > > > > > > > +1, I haven't seen any case where the split-join topology > isn't > > made

[DISCUSS] Deprecate split-join enrichment topology in favor of unified enrichment topology

Fellow Metronians, We've had the unified enrichment topology around for a number of months now, it has proved itself stable, and there is yet to be a time that I have seen the split-join topology outperform the unified one. Here are some simple reasons to deprecate the split-join topology. 1.

Re: [DISCUSS] Adding Apache Knox

+1 to adding Knox. On Mon, Nov 5, 2018 at 1:39 PM Ryan Merriman wrote: > I want to open a discussion around adding Apache Knox to our architecture. > I believe there are some benefits it offers in a couple different areas: > >1. It provides a proxy to endpoints for commonly used

Re: [DISCUSS] Knox SSO feature branch review and features

. i.e. should we make this required or optional? I'm open to hearing opinions on this, but I'm inclined to keep this a pluggable option. Mike On Fri, Nov 9, 2018 at 2:42 PM Michael Miklavcic < michael.miklav...@gmail.com> wrote: > Thanks for the update Ryan. Per my earlier comments,

Re: [DISCUSS] Knox SSO feature branch review and features

imagine we'll deprecate JDBC-based authentication at some point > so that may be a good time to switch. > > What do people think about this approach? Concerns? Are there any huge > holes in this I'm not thinking about? > > I want to highlight that the work Simon did in his feature

Re: [DISCUSS] Deprecating MySQL

Thanks for the write up Simon. I don't think I see any major problems with deprecating the general sql store. However, just to clarify, Metron does NOT require any specific backing store. It's 100% JPA, which means anything that can be configured with the Spring properties we expose. I think the

Re: [DISCUSS] Deprecating MySQL

tel and > profiles. Hence it ended up in Hbase, as a conveniently present data store > that matched the usage patterns. See > https://lists.apache.org/thread.html/145b3b8ffd8c3aa5bbfc3b93f550fc67e71737819b19bc525a2f2ce2@%3Cdev.metron.apache.org%3E > and METRON-1337 for discus

Re: [DISCUSS] Deprecating MySQL

t; and METRON-1337 for discussion. > > Simon > > > On 13 Nov 2018, at 18:50, Michael Miklavcic > wrote: > > > > Thanks for the write up Simon. I don't think I see any major problems > with > > deprecating the general sql store. However, just to clarify, Metron doe

Re: [DISCUSS] Attribution and merging the Elasticsearch client migration

Yes, definitely. On Thu, Nov 15, 2018 at 2:01 PM Casey Stella wrote: > Can you at least rename your commits to have METRON-1834 prefixing them? > On Thu, Nov 15, 2018 at 15:19 Michael Miklavcic < > michael.miklav...@gmail.com> > wrote: > > > https://github.com/apache/

Re: [DISCUSS] Deprecating MySQL

. And I agree with James about pluggability and simplifying the surface area of options we expose to users via Ambari config. Best, Mike On Thu, Nov 15, 2018 at 12:14 PM Michael Miklavcic < michael.miklav...@gmail.com> wrote: > Incidentally, even without the Metron piece in the pict

Re: [DISCUSS] Deprecating MySQL

user can still do so by > extending our abstractions if that is what they chose to do, but this would > not be officially supported by us. We would not be providing a config or > an mPack to do this. A user would have to do it on their own. > > James > > > > 15.11.2018, 12:15, &quo

Re: [DISCUSS] Deprecating MySQL

.org/thread.html/145b3b8ffd8c3aa5bbfc3b93f550fc67e71737819b19bc525a2f2ce2@%3Cdev.metron.apache.org%3E > and METRON-1337 for discussion. > > > > Simon > > > >> On 13 Nov 2018, at 18:50, Michael Miklavcic < > michael.miklav...@gmail.com> wrote: > >>

Re: [DISCUSS] Attribution and merging the Elasticsearch client migration

I'm attempting 1 more option, which would be to do a "git merge --strategy-option theirs" after having done the commit wrangling in the PR branch. Will reply back with results. On Thu, Nov 15, 2018 at 2:02 PM Michael Miklavcic < michael.miklav...@gmail.com> wrote: > Yes, def

Re: [DISCUSS] Attribution and merging the Elasticsearch client migration

he > latest attempt doesn't work, I'm in favor of getting it in and just getting > it down to as few commits as reasonably possible. > > On Thu, Nov 15, 2018 at 4:12 PM Michael Miklavcic < > michael.miklav...@gmail.com> wrote: > > > I'm attempting 1 more option, which

Re: [DISCUSS] Attribution and merging the Elasticsearch client migration

ate Elasticsearch from TransportClient to new Java REST API (cstella via mmiklavc) [cstella] * | 0c4c622b 2018-11-14 | METRON-1749 Update Angular to latest release in Management UI (sardell via nickwallen) closes apache/metron#1217 [sardell] On Thu, Nov 15, 2018 at 4:29 PM Michael Miklavcic < michael.

Re: [DISCUSS] Attribution and merging the Elasticsearch client migration

.put("type", "float"); 207 properties.put("latitude", floatType); 208 Map doubleType = new HashMap<>(); 209 doubleType.put("type", "double"); 210 properties.put("score", doubleType); 211 } On Thu, Nov 15, 2018

Re: [DISCUSS] Knox SSO feature branch review and features

uthentication. To > > be > > > able to use Knox, you would have to upgrade to LDAP-based > authentication > > if > > > you were still using JDBC-based authentication in REST. The urls would > > > also change obviously. > > > > > > On Sun, Nov 11

[DISCUSS] Attribution and merging the Elasticsearch client migration

https://github.com/apache/metron/pull/1242 TL;DR I'd like to discuss the best option to merge METRON-1834 into master. I want to propose handling this like a feature branch and merging it as-is. --- I'm sure most folks' initial reaction will be some skepticism akin to "have you tried turning it

Re: [DISCUSS] Deprecate split-join enrichment topology in favor of unified enrichment topology

The PR has now been merged into master and closed. https://issues.apache.org/jira/browse/METRON-1855 On Sat, Nov 3, 2018 at 6:47 PM Michael Miklavcic < michael.miklav...@gmail.com> wrote: > PR is out here - https://github.com/apache/metron/pull/1252 > > I made the unified enri

Re: [DISCUSS] Slack Channel Use

one seen this or have insight or a > > starting point?" and "I'm seeing something weird in our tests" type stuff > > User list for usage and troubleshooting questions. Generally, > discussions > > like this in Slack should be redirected to the user list. > >

Re: [DISCUSS] Slack Channel Use

list / Jira / PRs as usual for any actual decisions + concrete > feature > > discussion/review. > > Slack for Metron development "Hey, anyone seen this or have insight or a > > starting point?" and "I'm seeing something weird in our tests" type stuff &g

Re: Invite to Slack Channel

Sent On Wed, Oct 3, 2018 at 8:17 AM Shane Ardell wrote: > Hello everyone, > > Is it possible for someone to send me an invite to the Metron Slack > channel? > > Regards, > Shane >

Re: [DISCUSS] Add e2e step to PR checklist

@Shane Just how much time are we talking about, on average? I don't think many in the community have had much exposure to running the e2e tests in their current form. It might still be worth it in the short term. On Tue, Oct 2, 2018 at 10:20 AM Shane Ardell wrote: > The protractor-flake package

Re: [DISCUSS] Feature Branch guidance

architectural changes. Architectural changes are limited based on the > discuss thread unless further discussion occurs. To close the feature > branch, start a DISCUSS thread to outline branch state and solicit overall > feedback and requests. The branch can be committed after codify

Re: [DISCUSS] Feature Branch guidance

+1 to those 2 bullet points Casey. And thanks Justin for adding the Jira for fixing the website. I can think of 2 good examples to borrow from recently that were submitted by community contributors. Shane Ardell brought up a discussion about migrating from Protractor to Cypress, and Tamas Fodor

Re: Bro plugin release process docs?

+1 to all of that from me, Jon. Thanks for taking care of this. On Wed, Oct 10, 2018 at 2:34 PM zeo...@gmail.com wrote: > I wonder if we should also update the > https://cwiki.apache.org/confluence/display/METRON/Release+Process > instructions > to include tagging for the bro plugin, or if we

Re: Metron dev environments moving to require Ansible 2.4+

I ran it up a second time and it seems to be working now. I'm not sure what happened there, but I'll keep an eye on it. On Mon, Oct 1, 2018 at 2:48 PM Nick Allen wrote: > I have been able to spin-up a development environment today without a > problem. > > On Mon, Oct 1, 2018 at 3:5

Re: Metron dev environments moving to require Ansible 2.4+

Anyone run latest master today with full dev? I'm seeing NoClassDefFoundError exceptions on starting enrichments. I upgraded to latest Ansible and the provisioning part seemed to work just fine. https://gist.github.com/mmiklavc/56205526b4736e859aa7ba52468ff4f3 On Mon, Oct 1, 2018 at 6:46 AM

Re: [DISCUSS] Migrate from Protractor to Cypress

Shane, Can you elaborate on the testing model you're proposing? I looked through the overview and some of the documentation. As far as I can tell, this would effectively be and e2e test for the UI *only*, so we would be missing testing the actual integration points with the REST API or any other

Re: [DISCUSS] Migrate from Protractor to Cypress

I'm good with it. We can see some tests in action (and hopefully running in Travis! :-D) and then migrate and deprecate Protractor accordingly if we still agree that's the way to go. When you submit the first PR, please link to this DISCUSS via permalink from the mailing list archives. Thanks

Re: [DISCUSS] Replacing Moment.js with date-fns or native functions

Sounds reasonable to me as well. Thank you for detailed explanation, examples, and risk assessment! When you submit the PR for this, please link back to the DISCUSS via permalink from the mailing list archives. +1 Thanks, Mike On Wed, Sep 26, 2018 at 6:40 AM Casey Stella wrote: > I think it's

Re: [DISCUSS] Batch Profiler Feature Branch

> > > > > -- > > [1] https://issues.apache.org/jira/browse/METRON-1787 > > [2] https://issues.apache.org/jira/browse/METRON-1788 > > [3] https://issues.apache.org/jira/browse/METRON-1789 > > > > > > > > > > > > > > On Thu,

Re: [DISCUSS] Batch Profiler Feature Branch

I think I'm torn on this, specifically because it's batch and would generally be run as-needed. Justin, can you elaborate on your concerns there? This feels functionally very similar to our flat file loaders, which all have inputs for config from the CLI only. On the other hand, our flat file

Re: [DISCUSS] Batch Profiler Feature Branch

? > > You would just get a profile that is slightly different over the entire > time span. This is not a new risk. If the user changes their Profile > definitions in Zk, the same thing would happen. > > > On Thu, Sep 20, 2018 at 12:15 PM Michael Miklavcic < > michael.mik

Re: [DISCUSS] Batch Profiler Feature Branch

ght? :) > > So it kind of works, but it is definitely not ideal for use case 3. I > could add --begin and --end args to constrain the time frame over which the > Batch Profiler runs. I do not have that in the feature branch. It would > be easy enough to add though. > > &g

Re: [DISCUSS] Migrate from Protractor to Cypress

tps://docs.cypress.io/guides/getting-started/testing-your-app.html#Stubbing-the-Server > > On Thu, Sep 20, 2018 at 12:09 AM Michael Miklavcic < > michael.miklav...@gmail.com> wrote: > > > Shane, > > > > Can you elaborate on the testing model you're proposing? I

Re: [DISCUSS] Batch Profiler Feature Branch

an error doesn't force you to re-run over the entire history. Same goes for testing out the profile seeing batch job in the first place. On Thu, Sep 20, 2018 at 11:23 AM Nick Allen wrote: > Assuming you have 9 months of data archived, yes. > > On Thu, Sep 20, 2018 at 1:22 PM Michael

Re: [DISCUSS] Attribution and merging the Elasticsearch client migration

easier for people. On Fri, Nov 16, 2018, 5:42 AM Otto Fowler > Maybe this is worth a confluence entry, not as a guide, but just to > document what you did. > > On November 15, 2018 at 19:07:40, Michael Miklavcic ( > michael.miklav...@gmail.com) wrote: > > Ok, this is

Re: [DISCUSS] Knox SSO feature branch review and features

etron/pull/1266. > > > 2) Yes Knox is a service you can install with Ambari, similar to Ranger > > or > > > Spark. There are some things that are specifically configured in Knox > and > > > there are some things specific to Metron. I will put up a PR with the > >

Re: [DISCUSS] Knox SSO feature branch review and features

ensure the developer experience doesn't > change. > > On Fri, Nov 16, 2018 at 10:47 AM Michael Miklavcic < > michael.miklav...@gmail.com> wrote: > > > Ryan, what's remote debugging look like for UI testing with Knox enabled? > > Anything we lose from a dev testability standpoint

Re: [DISCUSS] Writer class refactor

Thanks for the write up, Ryan. I had to touch on some of this when refactoring the kafka writer away from the async model so we could guarantee delivery. We had potential to drop messages before that change because of the async producer calls, which would ack the Storm tuple as soon as the writer

Re: [ANNOUNCE] Apache Metron release 0.7.0

And a big thanks to Justin Leet for being our release manager. Great work Justin! On Mon, Dec 17, 2018 at 10:07 AM Justin Leet wrote: > Hi all, > > I’m pleased to announce the release of Metron 0.7.0! There's been a lot > of work on improvements, upgrades, discussion, and more. Thanks to

Re: Site-book broken in master

+1 for merging a fix. > > > > On December 20, 2018 at 12:43:57, Michael Miklavcic ( > michael.miklav...@gmail.com) wrote: > > Thanks for the feedback Otto. I'm not too familiar with our infrastructure > afa impact of switching to ascii doc, but I think it's worth consi

[DISCUSS] Metron documentation improvements

We recently had our site-book doc generation break due to our not including it in the Travis build. The fix for a broken build seems simple enough - add it to our build process and assuming it doesn't cause build timeout issues, we should be good to go. Beyond that, there are additional issues

Re: Site-book broken in master

Fowler (ottobackwa...@gmail.com) > wrote: > > What would help is an automated test the tests all the links as well. > > > > On December 19, 2018 at 19:55:03, Michael Miklavcic ( > michael.miklav...@gmail.com) wrote: > > I'd also like to submit a call for suggestions for making

Re: [DISCUSS] Metron documentation improvements

we want to go. I'm a +0 > > On Thu, Dec 20, 2018 at 2:47 PM Michael Miklavcic < > michael.miklav...@gmail.com> wrote: > > > We recently had our site-book doc generation break due to our not > including > > it in the Travis build. The fix for a broken build seems si

Re: [DISCUSS] Mandatory relocation of Apache git repositories on git-wip-us.apache.org

If it's the option I'm picturing, I've used that for merging in a PR against my PR. It's pretty simple and I don't recall it allowing options for fitting our format. Unless I'm mistaken or that has changed, I'd recommend our current workflow. On Mon, Dec 10, 2018 at 3:26 PM Justin Leet wrote: >

Re: [DISCUSS] Metron documentation improvements

et to ensure you're not > checking domains linked from our docs and turn travis into google. ;) > > > On Thu, Dec 20, 2018 at 3:19 PM Michael Miklavcic < > michael.miklav...@gmail.com> wrote: > > > Well golly, I love this. I'll give that a whirl! > > > > On Th

[DISCUSS] Handling dropped messages in REGEX_SELECT with Kafka topic routing

When a message is filtered by the message filtering mechanism, we explicitly drop the message (and presumably ack it in Storm), as explained here - https://github.com/apache/metron/tree/master/metron-platform/metron-parsing#filtered. When using the REGEX_SELECT field transformation (see here -

Site-book broken in master

FYI, site-book is currently broken in master. I think I've found the source of the issue and will be issuing a fix shortly. Best, Mike

Re: [DISCUSS] Deprecate split-join enrichment topology in favor of unified enrichment topology

20, 2018 at 11:01 AM Michael Miklavcic < michael.miklav...@gmail.com> wrote: > Thanks for pointing that out Ali. I created a ticket to track it - > https://issues.apache.org/jira/browse/METRON-1889 > > On Mon, Nov 19, 2018 at 11:51 PM Ali Nazemian > wrote: > >> Hi, >

Re: [DISCUSS] Remove `/api/v1/update/replace` endpoint

+1 to that Nick On Fri, Dec 7, 2018 at 11:13 AM Nick Allen wrote: > Heads up - I have not received a response from anyone for about 3 days. I > am going to take that as no one has a problem with this change. I will > likely merge the PR today. > > > > On Tue, Dec 4, 2018 at 4:05 PM Nick Allen

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

ng flushed (nickwallen) closes apache/metron#1194 > > > > > > > > > METRON-1717 Relocate Storm Profiler Code (nickwallen) > > > closes > > > > > > > > > apache/metron#1187 > > > > > > > >

Re: Authorization for Configuration

expect anything covered by the ZK configs to be done as part of > this effort (possibly in stages). As noted, I would expect this to be a > feature branch rather than piecemeal replacement. > > @Mike Yeah, I agree. The Jira for that doesn't exist yet, pretty much > pending this ex

[DISCUSS] Managing intermittent test failures

Every now and then we see intermittent test failures, and rather than sweeping them under the rug, we should have a simple method to track and handle them. I started creating Jiras for tests that I've seen fail, but that don't fail consistently, or even fail more than once. For example,

Re: [DISCUSS] Managing intermittent test failures

I added a comment here - https://cwiki.apache.org/confluence/display/METRON/Reporting+Issues On Thu, Nov 29, 2018 at 9:22 AM Casey Stella wrote: > +1, I'd say mention it on the dev list and slack channel. > > On Thu, Nov 29, 2018 at 10:26 AM Michael Miklavcic < > michael.mikl

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

d before we're set to move forward with a core > release (or we choose not to fix it, given the current version is > affected), I'm happy to put out a new RC. > > On Mon, Dec 3, 2018 at 4:12 PM Michael Miklavcic < > michael.miklav...@gmail.com> wrote: > > > +1 Nick > &

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

I have one more intermittent failure to add to the list from a timeout in the profiler integration tests. https://issues.apache.org/jira/browse/METRON-1918 On Mon, Dec 3, 2018 at 2:54 PM Michael Miklavcic < michael.miklav...@gmail.com> wrote: > fwiw, I have not been able to

Re: [DISCUSS] Recurrent Large Indexing Error Messages

Thanks for putting this together Nick. For point 2, I believe this was the relevant comment from that thread - https://github.com/apache/metron/pull/453#issuecomment-283349461 I'm partial to a combo of option 3 (the 2nd #2 listed) or 4. I would want to: - Not bog down indexing for good

<    1   2   3   4   >