[GitHub] metron issue #873: METRON-1367 Stellar should have some instrumentation of f...

Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/873 If there are any ideas on improving the tags implementation I would love to here them ---

[GitHub] metron issue #873: METRON-1367 Stellar should have some instrumentation of f...

Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/873 The last commit adds in the ability to tag timings, and to filter on those tags in the shell when calling %timing. LambdaExpressions are now timed as well. When Lambdas are used with

Re: [DISCUSS] Overcoming developer inertia when spinning up new environments

A bus factor of > 1? One main requirement would be that the implementation of the deployment has to be done and documented in such a way that it is maintainable. I *think* if this was done in chucks, and under review and better yet more collaboration, that would be possible. Another would be som

[GitHub] metron issue #874: METRON-1372 Validate JIRA for Releases

Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/874 +1 worked great ---

[GitHub] metron pull request #874: METRON-1372 Validate JIRA for Releases

Github user nickwallen commented on a diff in the pull request: https://github.com/apache/metron/pull/874#discussion_r157632089 --- Diff: build_utils/release-utils/validate-jira-for-release --- @@ -0,0 +1,197 @@ +#!/bin/bash +# +# Licensed to the Apache Software Foundat

[DISCUSS] Overcoming developer inertia when spinning up new environments

I want to revisit the idea of providing an alternative container-based approach (Docker, Kubernetes, etc) to spinning up Metron that is faster and uses less resources (a "Metron light"). This would provide a way for reviewers to more quickly review and test out changes. Full dev with ansible will

[GitHub] metron pull request #874: METRON-1372 Validate JIRA for Releases

Github user ottobackwards commented on a diff in the pull request: https://github.com/apache/metron/pull/874#discussion_r157605768 --- Diff: build_utils/release-utils/validate-jira-for-release --- @@ -0,0 +1,197 @@ +#!/bin/bash +# +# Licensed to the Apache Software Foun

Re: [MEETING NOTES] 12/18/17 Developer Community Meeting

Please not: 1. Feel free to comment on anything here on the list 2. It is not Jon Zeolla’s fault that the formatting is wrong On December 18, 2017 at 14:52:36, Otto Fowler (ottobackwa...@gmail.com) wrote: 2017-12-18 Dev Community Meeting Agenda - Call for reviewers, ideas how to get mo

[MEETING NOTES] 12/18/17 Developer Community Meeting

2017-12-18 Dev Community Meeting Agenda - Call for reviewers, ideas how to get more involvement, what people can do to help (Otto Fowler) - Feature branches : we have two now, what are they and how are we going to work on them (Otto Fowler) - ES 5.6 upgrade (Michael Mik

[GitHub] metron issue #869: METRON-1362 Improve Metron Deployment README

Github user nickwallen commented on the issue: https://github.com/apache/metron/pull/869 @justinleet I made the 'warning' that you suggested. Take a look and let me know if that works. ---

[GitHub] metron pull request #874: METRON-1372 Validate JIRA for Releases

GitHub user nickwallen opened a pull request: https://github.com/apache/metron/pull/874 METRON-1372 Validate JIRA for Releases Adds a script that helps the Release Manager validate JIRA for a pending release. Help is printed along with an example. ``` $ ./release-ut

Re: UPDATE MEETING December Developer Community Meeting

13 minute warning On December 17, 2017 at 15:56:21, Nadir Hajiyani (nadir.hajiy...@gmail.com) wrote: Aah, just noticed it in the middle of the email - 12.30 pm EST - hit send too early. Thanks. On Sun, Dec 17, 2017 at 2:54 PM, Nadir Hajiyani wrote: > Hi, > What time is this meeting at? > > T

[GitHub] metron pull request #840: METRON-939: Upgrade ElasticSearch and Kibana

Github user justinleet commented on a diff in the pull request: https://github.com/apache/metron/pull/840#discussion_r157540768 --- Diff: metron-platform/metron-elasticsearch/README.md --- @@ -33,7 +42,217 @@ For instance, an `es.date.format` of `.MM.dd.HH` would have the conse

[GitHub] metron pull request #840: METRON-939: Upgrade ElasticSearch and Kibana

Github user justinleet commented on a diff in the pull request: https://github.com/apache/metron/pull/840#discussion_r157540388 --- Diff: metron-platform/metron-elasticsearch/README.md --- @@ -1,5 +1,14 @@ # Elasticsearch in Metron +## Table of Contents + +* [

Re: [DISCUSS] Upcoming Release

Once we have the area, I can do the same for the RC check script On December 18, 2017 at 11:11:18, Nick Allen (n...@nickallen.org) wrote: Sure, I can clean up the script a bit and submit a PR for it. Jon and Otto asked that I open a PR on the script that I use for merging PRs too. On Fri, Dec

Re: [DISCUSS] Upcoming Release

Sure, I can clean up the script a bit and submit a PR for it. Jon and Otto asked that I open a PR on the script that I use for merging PRs too. On Fri, Dec 15, 2017 at 2:30 PM, Matt Foley wrote: > Perhaps under “build_utils” we should add a subdirectory for > “release_utils”. > > From: Casey St

Re: [DISCUSS] Support Ubuntu Installs in the MPack

Here are the JIRAs that fell out of this discussion. Work will progress in this order. - METRON-1351 Create Installable Packages for Ubuntu Trusty - METRON-1371 Enhance Mpack for Ub

[GitHub] metron issue #870: METRON-1364: Add an implementation of Robust PCA outlier ...

Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/870 How can we test this? ---

[GitHub] metron issue #873: METRON-1367 Stellar should have some instrumentation of f...

Github user ottobackwards commented on the issue: https://github.com/apache/metron/pull/873 One idea for a follow on : add a 'tag' or 'type' similar to log.INFO log.DEBUG to the records, so that you can filter the output. ---