Re: So we graduated...

Really exciting! Congrats to the founding team! --Matt On 4/20/17, 4:02 PM, "Houshang Livian" wrote: Congratulations Team. Great work! On 4/20/17, 2:55 PM, "larry mccay" wrote: >Wonderful news and well deserved!

Re: [DISCUSS] next release proposal

in (or mostly in) the 0.4.0 branch. Thanks, --Matt On 4/18/17, 5:30 PM, "Matt Foley" <ma...@apache.org> wrote: Thanks, we’re now up to 4 backward-incompatible issues. Any others should be so marked? On 4/17/17, 4:43 PM, "Matt Foley" <ma...@apache.or

Re: profiler Syntax error

Good eye, Otto! From: Otto Fowler <ottobackwa...@gmail.com> Date: Wednesday, August 2, 2017 at 2:12 PM To: Matt Foley <mfo...@hortonworks.com>, "dev@metron.apache.org" <dev@metron.apache.org>, "u...@metron.apache.org" <u...@metron.apache.org> Sub

Re: profiler Syntax error

Hi Dima, Is it possible that the input parser is giving an unreasonable value for “destination_ip”? Or perhaps fails to provide an end quote for that value? Does this profile fail on the first message to be consumed, or does it get a ways into the data stream and then choke? In either case,

Re: [DISCUSS] Code Reformatting next steps

Regarding METRON-1087, I’m in favor of freezing commits for a day, to let Justin re-run the script for METRON-1087 over all of current master, and commit it. Perhaps, for assurance, this commit should only include the fully-automated “vast majority”; the couple dozen files that needed manual

Re: [DISCUSS] Code Reformatting next steps

nk it'll make my life easier too. At that point, I'll just kill the existing PR and put out new ones when I have some free time. On Fri, Aug 11, 2017 at 2:42 PM, Matt Foley <mfo...@hortonworks.com> wrote: > We can wait until 777 goes in, but any sma

Re: [GitHub] metron pull request #530: METRON-777 Metron Extension System and Parser Exte...

Eesh, sorry, please ignore. This was incorrect, due to reading two diff blocks as contiguous. On 8/16/17, 9:58 PM, "mattf-horton" wrote: Github user mattf-horton commented on a diff in the pull request:

Re: [DISCUSS] METRON-994 -> Rest v. Stellar ( api of record )?

Hi all, At the risk of getting suddenly unpopular (:-) I would like to argue the other side. Architecturally I disagree with having REST invoke Stellar, or in general making Stellar the single point of contact for management functionality. Several reasons: 1. The architectural component

Re: [DISCUSS] METRON-994 -> Rest v. Stellar ( api of record )?

hat both call? On Fri, Jul 7, 2017 at 2:36 PM, Matt Foley <ma...@apache.org> wrote: > Hi all, > At the risk of getting suddenly unpopular (:-) I would like to argue the > other side. > Architecturally I disagree with having REST invoke Stellar, o

Re: [VOTE][PROPOSAL] minor changes to release process

Vote passes with +1 : 4 votes (3 binding, 1 non-binding) 0 : none -1 : none I’ll edit the doc to reflect the change. Thanks, --Matt On 7/6/17, 10:53 AM, "Matt Foley" <mfo...@hortonworks.com on behalf of ma...@apache.org> wrote: Thanks, all. That’s 3 binding +1’s, so I’m

Re: [Request for Consensus Approval] dev branch for Stellar additional work

ke sure it isn't overlooked. Jon On Wed, Jul 5, 2017 at 4:40 AM Matt Foley <ma...@apache.org> wrote: > Now that METRON-877 is in, I would like to proceed with Steps 3-6 of the > remaining work to separate out Stellar functionality as an independent &g

Re: [VOTE][PROPOSAL] minor changes to release process

changes, please bring it up and we’ll correct. Thanks, --Matt On 7/5/17, 2:47 PM, "Matt Foley" <ma...@apache.org> wrote: (The below proposal is also stated in https://issues.apache.org/jira/browse/METRON-1020 ) The following proposed changes are small, but not just edi

Re: [DISCUSSION] METRON-1046 -> Stellar Files for multiple statement execution

1.0 ... This section describes the structure of a JSON API document, which is ... [Note: this references JSON Pointer as a standard entity [RFC6901] but not as part of the JSON spec.] From: Otto Fowler <ottobackwa...@gmail.com> Date: Friday, July 14, 2017 at 10:42 AM To: Matt Foley <mfo...@h

Re: [DISCUSS] Easing the ramp-up into contributing

Really good discussion thread, thanks for opening it Justin. I’m a fan of adding javadocs to the publicly available doc set. It’s not the most important of the items listed below, but it is easy, and will push people to be more attentive to dev documentation. METRON-759 is open for that, and

Re: [DISCUSS] Persisting user data

There’s a couple other places you could put config info (but maybe not saved searches): - Zookeeper - metron-alerts-ui/config.xml or config.json file - the Ambari database, whichever it happens to be Questions that influence the decision include: 1. Should there be one configuration shared

code review: adding time-based flushing to BulkMessageWriterBolt

I think PR#481, for the first two-thirds of METRON322 (sub-tasks 2, 3, 4, and 7), is ready for review and inclusion.  If folks have time to review it would be appreciated. Thanks, --Matt

Re: [VOTE] Apache Metron 0.4.0 release

indices [PASS] >> > * Metron YAF Zeppelin dashboard with sample ingested YAF data [PASS] >> > * Management UI and REST Swagger UI sanity check [PASS] >> > >> > >> > -Anand >> > >> > >> &g

Re: [VOTE] Apache Metron 0.4.0 release

- verified data in Kibana On Fri, Jun 30, 2017 at 12:24 PM, Matt Foley <mfo...@hortonworks.com> wrote: > Hey all, we need more votes! > > So far we have 6 +1’s (including mine) and no 0’s or -1’s. > BUT, only two are binding, ie from

Re: [GitHub] metron issue #616: METRON-877 Extract core implementation and UDF support, c...

Yes, it could cause problems. Not sure what to do about it. Should we open an INFRA ticket, or does our PMC have auth to poke it? One can browse the (real) Apache repo and see it, it hasn't been pushed from there. --Matt On Mon, Jul 3, 2017 at 4:16 AM -0700, "Otto Fowler"

Re: PLEASE DON'T COMMIT TO APACHE METRON until propagation issue is fixed

e should be good to go at this point. Any objections, Matt? On Mon, Jul 3, 2017 at 2:39 PM, Matt Foley <mfo...@hortonworks.com> wrote: > https://issues.apache.org/jira/browse/INFRA-14502 has been opened. > > On 7/3/17, 11:25 AM, "Matt F

PLEASE DON'T COMMIT TO APACHE METRON until propagation issue is fixed

It seems propagation from git-wip-us.apache.org/repos/asf/metron to github.com/apache/metron is currently broken. If you browse https://git1-us-west.apache.org/repos/asf?p=metron.git you see that commit a5b13777a, for METRON-877, was committed yesterday but is still not present in github:

Re: PLEASE DON'T COMMIT TO APACHE METRON until propagation issue is fixed

https://issues.apache.org/jira/browse/INFRA-14502 has been opened. On 7/3/17, 11:25 AM, "Matt Foley" <mfo...@hortonworks.com> wrote: It seems propagation from git-wip-us.apache.org/repos/asf/metron to github.com/apache/metron is currently broken. If you browse

[Request for Consensus Approval] dev branch for Stellar additional work

Now that METRON-877 is in, I would like to proceed with Steps 3-6 of the remaining work to separate out Stellar functionality as an independent module. A couple people have suggested that this further development should be done in a Metron “dev branch”, where: a) changes are more visible than

Re: [Request for Consensus Approval] dev branch for Stellar additional work

And another way suggested by Jon’s statement, is to not squash the commit, but leave at least one of each committer’s contributions intact. That might not be too hard to add to the prepare-commit script, it’s just an invocation of interactive rebase/squash. On 7/5/17, 10:32 AM, "Matt

Re: [Request for Consensus Approval] dev branch for Stellar additional work

Okay, I’ll undertake to add to the committer’s guide before the first PR. From: Otto Fowler <ottobackwa...@gmail.com> Date: Wednesday, July 5, 2017 at 6:28 AM To: "dev@metron.apache.org" <dev@metron.apache.org>, Matt Foley <ma...@apache.org> Subject: Re: [Re

Re: [Request for Consensus Approval] dev branch for Stellar additional work

g we do properly squash merge into the speculative branch). Not a big issue though, I guess, just need to make sure it isn't overlooked. Jon On Wed, Jul 5, 2017 at 4:40 AM Matt Foley <ma...@apache.org> wrote: > Now that METRON-877 is in, I would like

[VOTE][PROPOSAL] minor changes to release process

(The below proposal is also stated in https://issues.apache.org/jira/browse/METRON-1020 ) The following proposed changes are small, but not just editorial in nature, hence will require vote of the community to change. Our bylaws don’t have an action type of Modifying Policy, but it’s probably

Re: [VOTE][PROPOSAL] minor changes to release process

that makes a lot of sense. On Wed, Jul 5, 2017 at 5:47 PM, Matt Foley <ma...@apache.org> wrote: > (The below proposal is also stated in https://issues.apache.org/ > jira/browse/METRON-1020 ) > > The following proposed changes are small, but not jus

[ANNOUNCE] Apache Metron 0.4.0 release

Friends and Colleagues, I’m happy to announce the completion and release of Apache Metron 0.4.0. Besides a bunch of great new features, this is also our first release as a TLP. The public website at http://metron.apache.org/ has been updated and has correct links to the new downloads and docs.

Re: [ANNOUNCE] Apache Metron 0.4.0 release

BTW, if you’ve recently accessed any URIs under http://metron.apache.org/, you may need to hit “refresh” in your browser to see the new updated versions. On 7/5/17, 1:35 PM, "Matt Foley" <ma...@apache.org> wrote: Friends and Colleagues, I’m happy to announce the comple

Re: Status of METRON-153

FWIW, we know that several of the changes in the (recently committed) METRON-634 Mpack bug fixes and improvements, not impacting Ambari database (PR#532) are necessary for a smooth install on Centos7. These changes are for the manual install wizard, but all the non-“description” changes

Re: [VOTE] Metron 0.4.0 release (RC2)

I’ve opened https://issues.apache.org/jira/browse/METRON-905 to fix both the default i/f and the square brackets issue. On 4/28/17, 10:30 AM, "Matt Foley" <mfo...@hortonworks.com> wrote: I’m happy to re-spin with a default of binding to all interfaces (0.0.0.0) With tha

Re: Facing error whith mvn clean install

Well, Linux in general at least. CentOS 7 is known to work fine. Ubuntu has worked most of the time; Ryan’s PR#669 today was to stabilize another bit of it. On 7/28/17, 9:13 AM, "Laurens Vets" wrote: I highly suspect the fact that you're trying to compile Metron on

Re: Code style change requires vote?

Hi Justin, Technically, acceptance into the code base with appropriate review and +1’s signifies lazy consensus of all committers (since any committer can blackball a PR with a single justified -1). If you (or any community member) is concerned that people didn’t have sufficient opportunity to

[DISCUSS] Metron release 0.4.1

Hello all, At the meeting this morning, the community expressed the wish to create a new release, to be a point release and not including METRON-777. Therefore, I propose to create release 0.4.1 from Metron master branch, with whatever additional commits the community considers vital and can

Request double-check on Ambari config logic (ES network_host)

Hi, there have been widely varying statements about what needs to be in the Elasticsearch config parameter “network_host”. I think I may have a rationale for what works and what doesn’t, but I’d like your input or correction. I am focusing on what worked in terms of punctuation (quotes and

Re: Request double-check on Ambari config logic (ES network_host)

Request double-check on Ambari config logic (ES network_host) As somebody who has systems that have globally-scoped addresses directly addressed onto servers, I would prefer using using "_local_", "_site_". Jon On Tue, May 2, 2017 at 1:36 PM Matt Foley <mfo...@hortonworks.com&

Re: Request double-check on Ambari config logic (ES network_host)

> > In a separate ES related JIRA I'm working on, I will either need to > de_dot > > bro fields in the parser, force the transformation in the Kafka plugin > (not > > preferred), provide an example of how to do this in bro configs (not very > &

Re: Remember remember the 29th of April — Matt’s instructions for handling the github rename

So Apache infra confirmed that they use github’s “rename” capability, so no one needs to worry about losing connection with their remote repositories. That means that doing any of the below is strictly voluntary, and B and D (changing upstream pointers) are completely unnecessary. If you want

Re: [INCOMING] Metron 0.4.0 release (RC3)

the unit tests. Thanks much, --Matt On 6/2/17, 11:36 AM, "Matt Foley" <mfo...@hortonworks.com on behalf of ma...@apache.org> wrote: Hi Christian, I agree this would be nice to have. I also agree with @kylerichardson ‘s review comments that the change (with field renames and o

Re: [INCOMING] Metron 0.4.0 release (RC3)

, METRON-701, METRON-503, METRON-503, METRON-503, METRON-743, METRON-646, METRON-686, METRON-742, METRON-741, METRON-740, METRON-728, METRON-733, METRON-690) On 6/26/17, 10:17 AM, "Matt Foley" <ma...@apache.org> wrote: Hi all, I am proceeding with building the 0.4.0 release

Metron Release rules

The Release Process document at https://cwiki.apache.org/confluence/display/METRON/Release+Process currently states that a file named DISCLAIMER is a required artifact in the release package. The contents of this file are: === Apache Metron is an effort undergoing incubation at The Apache

Re: Metron Release rules

> +1 Yes, definitely cruft. Good find. > > > > On Mon, Jun 26, 2017 at 9:50 PM, Matt Foley <ma...@apache.org> wrote: > > > > The Release Process document at https://cwiki.apache.org/ > > confluence/display/METRON/Release+Process

Re: [INCOMING] Metron 0.4.0 release (RC3)

On Thu, Jun 1, 2017, 6:03 PM Nick Allen <n...@nickallen.org> wrote: > Sounds good, Matt. Looking forward to cutting this release. > > On Thu, Jun 1, 2017 at 5:17 PM, Matt Foley <ma...@apache.org> wrote: > > > Hi all, > >

Re: [INCOMING] Metron 0.4.0 release (RC3)

I would also appreciate a +1 on https://github.com/apache/metron/pull/605 On 6/1/17, 4:02 PM, "Matt Foley" <mfo...@hortonworks.com> wrote: The METRON-976 patch looks short and sweet. If someone familiar with that chunk of code can +1 it, it can go in too. On

Re: Help needed in assign a Task

Hi Raghu, this is appropriate for the ‘dev’ list rather than the ‘user’ list, since you’re interested in joining in development work – which is great, welcome! :-) To enable jira assignment, someone must add your name to the project contributor list.  I’m sure our honored chairman has the

Re: [GitHub] metron issue #530: METRON-777 Metron Extension System and Parser Extensions

➢ Will MD files that are not README.md be pulled into site-book? Yes indeed. All md files are collected and used in the site-book. Md files named README are renamed to “index” and referenced by a friendly form of the directory name they are in. All other md files retain their name and

Re: Started the infrastructure requests to move to TLP

12:24:53AM -0700, Matt Foley wrote: >... > ‘B’ may or may not be important, depending on how > Apache INFRA goes about changing the name of the Github apache/metron > mirror repo. If they use the standard Github owner’s command > for renaming a repo, then Githu

Re: [VOTE] Metron 0.4.0 release (RC2)

RC2 is withdrawn, pending completion of the graduation transition and the fix for square brackets in ES config. Thanks, --Matt On 4/28/17, 1:27 PM, "Greg Stein" <gst...@gmail.com> wrote: On Thu, Apr 27, 2017 at 09:25:04PM -0700, Matt Foley wrote:

Re: Started the infrastructure requests to move to TLP

hings up to wait on my efforts because it could be weeks before it's entirely done and tested appropriately, I'm just wondering if that will be a natural byproduct of our graduation. Jon On Sat, Apr 29, 2017, 3:24 AM Matt Foley <ma...@apache.org> wrote: >

Re: Request double-check on Ambari config logic (ES network_host)

, but it needs testing. Thanks, --Matt From: Otto Fowler <ottobackwa...@gmail.com> Date: Tuesday, May 2, 2017 at 11:27 AM To: "d...@metron.incubator.apache.org" <d...@metron.incubator.apache.org>, Matt Foley <mfo...@hortonworks.com>, "dev@metron.apache.org" <

Re: Request double-check on Ambari config logic (ES network_host)

this causes what you’re seeing, but it seems feasible. From: Otto Fowler <ottobackwa...@gmail.com> Date: Tuesday, May 2, 2017 at 8:30 PM To: "d...@metron.incubator.apache.org" <d...@metron.incubator.apache.org>, Matt Foley <mfo...@hortonworks.com>, "dev@metron.ap

Re: [DISCUSS] Update Metron Release Documentation

al 0.4.0 release? I really only see a need to update the release documentation to account for this. Thanks, Jon On Mon, May 1, 2017 at 2:39 PM Matt Foley <ma...@apache.org> wrote: > In previous discussion threads, I proposed that the site should have a

Re: [DISCUSS] Code Style

+1. I originally suggested the Sun style as a starting point, and I find Justin’s arguments convincing, especially if there is a pre-packaged Google style checking plug-in. --Matt On 5/8/17, 9:47 AM, "Kyle Richardson" wrote: +1 Thanks, Justin. I'm all for

Re: [CALL FOR TEST DATA] Request help identifying public domain or opensource test data sets for Metron testing

- Dima On 10/08/2016 06:43 AM, Matt Foley wrote: Hi Dima, Sorry this is getting a little long, but TL;DR on Metron+Development+Environment+Setup+Instructions<https://cwiki.apache.org/confluence/display/METRON/Metron+Development+Environment+Setup+Instructions> is:

Re: Request double-check on Ambari config logic (ES network_host)

ot;eth0:ipv4" worked for me, I had modified the yaml.j2 template to include the square brackets. So the below theory is wrong. Back to the drawing board. Thanks, --Matt On 5/1/17, 3:08 PM, "Matt Foley" <ma...@apache.org> wrote: Hi, there have been widely vary

Re: Status of efforts to break stellar out?

Hi Otto, I just finished upgrading to the current code base, but need to tweak it to account for the last half dozen commits. After that I will post the first helping, that breaks out all the basic Stellar functionality, and some of the peripheral stuff, in a self-consistent and self-contained

Re: Zeppelin required for Metron 0.4.0 install

Dima, the Apache list server strips attachments for security and anti-spam reasons. You can post screenshots in Gist or Jira. On 6/5/17, 4:24 AM, "Dima Kovalyov" wrote: Thank you for prompt response Anand, I have attached screen.png one more time.

Re: Status of efforts to break stellar out?

Matt From: Otto Fowler <ottobackwa...@gmail.com> Date: Monday, June 5, 2017 at 2:33 PM To: "dev@metron.apache.org" <dev@metron.apache.org>, Matt Foley <ma...@apache.org> Subject: Re: Status of efforts to break stellar out? This is just breaking it out? Or are there

0.3.1 usages in node_modules

Colleagues, If one clones the current master, builds it with “mvn clean install –DskipTests”, and then cd’s to the root and invokes:     egrep  -r  '0\.3\.1'  * one gets a very large number of hits in metron-interface/metron-config/node and

Re: Question about the customization of Metron with my machine learining algo.

Hope you don’t mind if I chime in. There are a couple very basic points which are in the documentation, but may not jump out at a new user, who is trying to learn Metron at the same time as MaaS. 1. In the thread below there is only a brief reference to the main documentation page for MaaS,

Re: [VOTE] Apache Metron 0.4.0 release

nown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 7854 36A7 8258 6B71 829C 67A0 4169 AA27 ECB3 1663 On June 27, 2017 at 14:36:07, Mat

Re: Elasticsearch masters_also_are_datanodes doesn't work.

v@metron.apache.org> Cc: Michael Miklavcic <michael.miklav...@gmail.com>, Matt Foley <mfo...@hortonworks.com> Subject: Re: Elasticsearch masters_also_are_datanodes doesn't work. See inline. Now, Laurens, two question for you: First, please confirm: Are you setting the value

Re: [VOTE] Metron Release Candidate 0.4.1-RC4

to date, we have only one binding vote so far (thank you Nick) altho we also have 3 votes in favor from non-PMC committers. The rules permit the vote to remain open, so could a couple more PMC members please review and vote? Thanks, --Matt On 9/13/17, 1:24 PM, "Matt Foley&

[ANNOUNCE] Apache Metron Release 0.4.1

Many thanks to all who contributed, and enjoy your new release! Warm regards, --Matt Foley release manager

Re: Elasticsearch masters_also_are_datanodes doesn't work.

Sorry, you’ve beat me. Mike, what have you found in full-dev? Does ES work correctly there? From: Laurens Vets <laur...@daemon.be> Date: Wednesday, September 13, 2017 at 1:14 PM To: Matt Foley <mfo...@hortonworks.com> Cc: "dev@metron.apache.org" <dev@metron.apach

Re: [VOTE] Metron Release Candidate 0.4.1-RC4

o, YAF and snort - ingest into kafka topics and write indices [PASS] > > * Add squid telemetry, ingest into kafka topic and write indices [PASS] > > * Management UI and REST Swagger UI sanity check [PASS] > > > > Regards, > > Anand > >

Re: Elasticsearch masters_also_are_datanodes doesn't work.

; Date: Wednesday, September 13, 2017 at 2:08 PM To: Matt Foley <mfo...@hortonworks.com> Cc: Laurens Vets <laur...@daemon.be>, "dev@metron.apache.org" <dev@metron.apache.org> Subject: Re: Elasticsearch masters_also_are_datanodes doesn't work. Here's what I found. Data

Re: [VOTE] Metron Release Candidate 0.4.1-RC4

James Sirota" <jsir...@apache.org> wrote: +1 14.09.2017, 11:37, "Casey Stella" <ceste...@gmail.com>: > I ran it up and forgot to vote. +1 binding > - ran in full-dev > - verified signatures > - stellar works > &g

Re: [DISCUSS] Metron release 0.4.1

Looks like everything’s in now. Thanks very much everyone for the efforts! I’m spinning the RC and will have it out for vote shortly. --Matt On 9/7/17, 11:41 PM, "Matt Foley" <ma...@apache.org> wrote: METRON-1163 turns out to be invalid, due to a bad mav

Re: [DISCUSS] Metron release 0.4.1

Hi Ryan, yup, got it. It’s in. On 9/8/17, 1:25 PM, "Ryan Merriman" <merrim...@gmail.com> wrote: Matt, This was committed a few hours. I think you saw it but just wanted to make sure. Ryan > On Sep 7, 2017, at 11:26 AM, Matt Foley <m

Re: [VOTE] Metron Release Candidate 0.4.1-RC3

quot; + sys.argv[1]) ValueError: Unable to find these components: ch.hsr:geohash:jar:1.3.0:compile org.locationtech.spatial4j:spatial4j:jar:0.6:compile in the acceptable list of components: ./dependencies_with_url.csv I suspect GeoHash requires an update in the “dependencies_with_url.csv” file. T

Re: [DISCUSS] Metron release 0.4.1

METRON-1163 turns out to be invalid, due to a bad maven settings file. It is no longer an issue. Just waiting for the last couple items. On 9/7/17, 9:26 AM, "Matt Foley" <mfo...@hortonworks.com on behalf of ma...@apache.org> wrote: Okay. Please ping when committed.

Re: [DISCUSS] Metron release 0.4.1

> > > > > > On Tue, Aug 22, 2017 at 4:17 PM Matt Foley <ma...@apache.org> wrote: > > > Hello all, > > At the meeting this morning, the community expressed the wish to create a > > new release, to be a point release

Re: [DISCUSS] Metron release 0.4.1

fixes are still in review ( https://github.com/apache/metron/pull/729 and https://github.com/apache/metron/pull/730) and should make it in soon. It would be good to include these if possible. Ryan On Thu, Sep 7, 2017 at 12:23 AM, Matt Foley <ma...@apache.org> wrot

modified "Release Process" wiki

Hi, You may have seen notification for a change I made in the “Release Process” wiki page. The purpose of the change is to delay pushing the RC# tag to the public repo until AFTER one goes thru the verification steps on the release candidate. The reason is that on this release I’ve already

Re: Elasticsearch masters_also_are_datanodes doesn't work.

sticsearch expert, so if someone else knows different, please say so. Hope this helps more than obfuscates. --Matt From: Michael Miklavcic <michael.miklav...@gmail.com> Date: Tuesday, September 12, 2017 at 4:54 PM To: "dev@metron.apache.org" <dev@metron.ap

Re: [VOTE] Metron Release Candidate 0.4.1-RC3

> On Fri, Sep 8, 2017 at 7:38 PM, Matt Foley <ma...@apache.org> wrote: > >> Couple pieces of info that may affect your vote: >> >> 1. This does not include today’s commits of >> METRON-1162 Apply Live Messages to the Profile Debu

[VOTE] Metron Release Candidate 0.4.1-RC4

Colleagues, This is a call to vote on releasing Apache Metron 0.4.1. The release candidate is available at https://dist.apache.org/repos/dist/dev/metron/0.4.1-RC4/ Full list of changes in this release: https://dist.apache.org/repos/dist/dev/metron/0.4.1-RC4/CHANGES The github tag to be voted

Re: [DISCUSS] Metron release 0.4.1

, --Matt From: Matt Foley <mfo...@hortonworks.com> on behalf of Matt Foley <ma...@apache.org> Date: Tuesday, September 5, 2017 at 10:01 AM To: "dev@metron.apache.org" <dev@metron.apache.org> Subject: Re: [DISCUSS] Metron release 0.4.1 Great, working on it! From: Ni

Re: feature branch bumps

Hi all, Otto and I had an off-line discussion about this, and we think we have a constructive suggestion that will allow chunking the feature branch to some extent, which will of course make it easier to review. Otto is willing to make a series of PRs, each of which must be reviewed and

Re: [DISCUSS] Metron release 0.4.1

in by Friday. On Tue, Aug 29, 2017 at 1:35 PM, Matt Foley <ma...@apache.org> wrote: > Hi all, > Thanks for your inputs. The three PRs Nick mentioned have been > successfully closed. > Casey, do you have an ETA for these two PRs? (PR#709 and 717) > Thanks

Re: [DISCUSS] Metron release 0.4.1

> > >> The following PRs are usability enhancements for the Profiler. They > are > > >> fairly simple and I think are very helpful for troubleshooting. I > don't > > >> want to hold up the release, but it would be a "nice to have" to get > > thes

Re: [DISCUSS] Upgrading Elasticsearch from 2.x to 5.x

You can avoid the permission issues by attaching it to an Apache jira. On 10/11/17, 6:10 PM, "James Sirota" wrote: I can't see it. You probably want to link to a google drive 11.10.2017, 18:01, "Michael Miklavcic" : > I attached

Re: [DISCUSS] Release Process Update

I agree with Justin. This micro-feature is intended as a github widget, which causes the top-level README to give all viewers an immediate flag whether the build is healthy or not. It does not belong in a rendered site-book. Removing the widget during site-book build, can be done with a

Re: [DISCUSS] Upcoming Release

Hope everyone (at least in the U.S.) had a great Thanksgiving holiday. Regarding status of the release effort, still pending METRON-1252, so not making the release branch yet. Regards, --Matt On 11/17/17, 1:32 PM, "Matt Foley" <ma...@apache.org> wrote: (With rel

Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

[Please pardon me that the below is a little labored. I’m trying to understand the implications for both release and use, which requires some explanation as well as the two questions needed. Q1 and Q2 below are probably the same question, asked in slightly different contexts. Please consider

Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

munity. Unless we expect to do extensive iterative work on the plugin, which would then make the decision to spin it out now premature. Then again, I might be wrong ;) On November 27, 2017 at 19:58:11, Matt Foley (ma...@apache.org) wrote: [Please pardon me that the below is a little labored. I’m try

Re: [DISCUSS] Upcoming Release

include a release of the current state of the metron-bro-plugin-kafka. I will continue the discussion in that thread as to the process for accomplishing that, but plan on it happening. Regards, --Matt On 11/26/17, 6:26 PM, "Matt Foley" <ma...@apache.org> wrote: Hope ev

Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

is. It is how I have seen other projects like NiFi handle things as well. On December 4, 2017 at 17:14:41, Matt Foley (ma...@apache.org) wrote: Okay, looking at this from the perspective of making a release: We have two choices: a) I can s

Re: [DISCUSS] Stellar Documentation Autogeneration

+1 from me too, Justin. Great idea. On 12/14/17, 12:44 PM, "zeo...@gmail.com" wrote: A huge +1 from me. This would be great On Thu, Dec 14, 2017 at 3:39 PM Michael Miklavcic < michael.miklav...@gmail.com> wrote: > +1 from me, great idea Justin. I

[VOTE] Metron Release Candidate 0.4.2-RC2

Colleagues, This is a call to vote on releasing Apache Metron 0.4.2 and its associated metron-bro-plugin-kafka 0.1.0. The release candidate is available at https://dist.apache.org/repos/dist/dev/metron/0.4.2-RC2/ Full list of changes in this release:

Re: [DISCUSS] Upcoming Release

get attached to the release originate from? Does it get pulled out of JIRA or do they come from the commit log? My apologies for not staying on top of my JIRAs. On Tue, Dec 12, 2017 at 2:21 PM, Matt Foley <ma...@apache.org> wrote: > Thanks to Jon,

Re: [DISCUSS] Upcoming Release

Perhaps under “build_utils” we should add a subdirectory for “release_utils”. From: Casey Stella <ceste...@gmail.com> Date: Friday, December 15, 2017 at 10:50 AM To: "dev@metron.apache.org" <dev@metron.apache.org> Cc: Matt Foley <mfo...@hortonworks.com> Subject: Re

Re: [DISCUSS] Upcoming Release

(With release manager hat on) The community has proposed a release of Metron in the near future, focusing on Meta-alerts running in Elasticsearch. Congrats on getting so many of the below already done. At this point, only METRON-1252, and the discussion of how to handle joint release of the

Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

There’s two issues, I think: (1) We’d like to be able to version and evolve the main body of Metron and the metron-bro-plugin-kafka separately. (2) We want to be able to assure that each release of Metron has a known-working version of metron-bro-plugin-kafka At a very simple level, we can

Re: [DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

There’s two issues, I think: (1) We’d like to be able to version and evolve the main body of Metron and the metron-bro-plugin-kafka separately. (2) We want to be able to assure that each release of Metron has a known-working version of metron-bro-plugin-kafka At a very simple level, we can

Re: [DISCUSS] Upcoming Release

I’ve been listening. Looks like there are still a number of major issues to be committed first, right? The discussion on this thread constitutes sufficient engagement, I think, especially given the Subject line :-) Would the folks working on the 6 issues listed by Nick care to suggest a

Re: [DISCUSS] Upcoming Release

s the case would the next version be 0.4.3? Ryan On Fri, Nov 17, 2017 at 3:31 PM, Matt Foley <ma...@apache.org> wrote: > (With release manager hat on) > > The community has proposed a release of Metron in the near future, > focusing on Me

Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

Good, I’ll build the RC tonight. Thanks Jon. --Matt From: "zeo...@gmail.com" <zeo...@gmail.com> Date: Thursday, December 7, 2017 at 12:27 PM To: Matt Foley <mfo...@hortonworks.com> Subject: Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro' Otto, your un

  1   2   >