Re: [DISCUSS] Metron Release 0.6.0?

es apache/metron#1005 > > > > 4 months ago Merge remote-tracking branch 'origin/master' into > > > > feature/METRON-1416-upgrade-solr > > > > 4 months ago METRON-1526 Location field types cause DocValuesField > > appear > > > > more than once

Re: [DISCUSS] Metron Release 0.6.0?

to get that work done > asap. > > As of right now metron's dev ansible scripts pin to a specific release of > > metron-bro-plugin-kafka (0.1 > > <0.1https://github.com/apache/metron/blob/master/metron- > > deployment/ansible/roles/bro/vars/main.yml>), > > and I'm f

[DISCUSS] Release cadence

Hi all, In concert with the discuss thread on a potential 0.6.0 release, I'd also like start a discussion about our release cadence. We've generally been pretty relaxed around doing releases, and I'm curious what people's thoughts are on adopting a somewhat more regular schedule. Couple

Re: [DISCUSS] Metron Release 0.6.0?

looks like for a 1.0 release > and perhaps a more regular release schedule. I have some thoughts but > don't want to hijack this thread. > > Jon > > On Wed, Aug 15, 2018 at 9:11 AM Justin Leet wrote: > > > Hi all, > > > > It's been a little while since the las

[DISCUSS] Metron Release 0.6.0?

Hi all, It's been a little while since the last release, and a couple major items have gone in since then (or are hopefully close to going in!). In particular, I'd personally like to see a release with our Solr work and the close-to-completion

Re: [DISCUSS] Metron Parsers in Nifi

to parse asa ) or if the > goal is to have a hybrid approach coupling the processors/readers to the > metron installation. > > > On August 9, 2018 at 09:14:58, Justin Leet (justinjl...@gmail.com) wrote: > > I'll add onto Mike's discussion with the original set of requirem

Re: [DISCUSS] Metron Parsers in Nifi

t; > > > What would be the requirements or goals of metron integration with > Nifi? > > > How many levels or options for integration do we have? > > > What are the approaches to choose from? > > > Who are the target users? > > > > > > On Augus

Re: [DISCUSS] Metron Parsers in Nifi

n’t really necessary. A MetronRecordReader ( > either the megalithic or a reader per format ) would be a good approach. > Then have StellarTransformRecord processor that can do Stellar on _any_ > record, regardless of source. > > > > > On August 7, 2018 at 11:06:22, Justin

Re: [DISCUSS] Metron Parsers in Nifi

> way, not bolting the Metron composition > onto Nifi. Think of it like the Tao of Unix, the parsers and components > should be single purpose and simple, allowing > exceptional flexibility in composition. > > Comments inline. > > On August 7, 2018 at 09:27:01, Justin Lee

[DISCUSS] Metron Parsers in Nifi

Hi all, There's interest in being able to run Metron parsers in NiFi, rather than inside Storm. I dug into this a bit, and have some thoughts on how we could go about this. I'd love feedback on this, along with anything we'd consider must haves as well as future enhancements. 1. Separate

Re: Security Feature Branch?

+1 to feature branch. I agree it's probably a fairly hefty contribution that would benefit from being in a feature branch. On Thu, Jul 12, 2018 at 10:56 AM Casey Stella wrote: > I would support this being a feature branch. It sounds like a valuable but > large contribution. > > On Thu, Jul 12,

Re: [DISCUSS] Merging Solr feature branch (METRON-1416) into master

at 11:43:39, Justin Leet (justinjl...@gmail.com) wrote: > > The PR has two +1's at this point (and I'm implicitly +1). In the interest > of full disclosure, both are from people who made contributions of varying > degrees to the branch. > > Are there any objections to merging

Re: [DISCUSS] Merging Solr feature branch (METRON-1416) into master

new in terms of process. > > > > On Fri, Jun 22, 2018 at 12:53 PM Otto Fowler > wrote: > >> If all the PR’s are on master->feature branch. Why do we need testing? >> this is almost a vote situation. >> >> >> >> >> On June 22, 2018 at 12:01

Re: [DISCUSS] Merging Solr feature branch (METRON-1416) into master

1, 2018, 2:01 PM Nick Allen wrote: > > > +1 I think we should merge ASAP and kill the feature branch. I think the > > work has well surpassed the level required to get it into master. > > > > On Thu, Jun 21, 2018 at 1:20 PM, Justin Leet > > wrote: > > >

[DISCUSS] Merging Solr feature branch (METRON-1416) into master

Hi All, The Solr branch (/feature/METRON-1416-upgrade-solr ), has been progressing for a while now. I'd like to open up discussion around what it takes to get it into master. The JIRA for tracking this feature branch is

[ANNOUNCE] Apache Metron release 0.5.0

Hi All, I’m happy to announce the release of Metron 0.5.0! Everyone has put in a lot of working into improvements, new features, and discussion. Thanks to everyone who contributed, and I look forward to having users enjoy our new features and improvements. Details: The official release source

[RESULT][VOTE] Metron Release Candidate 0.5.0-RC2

The vote has passed. Including my +1, the voting was: 3 binding +1’s 1 non-binding +1’s no 0’s no -1’s. Release process is underway and will be announced to dev@ and user@ lists. Justin

Re: [VOTE] Metron Release Candidate 0.5.0-RC2

This includes a couple fixes from master, in particular two issues that were problematic, METRON-1586 <https://issues.apache.org/jira/browse/METRON-1586> and METRON-1544 <https://issues.apache.org/jira/browse/METRON-1544>. Justin On Thu, May 31, 2018 at 2:30 PM, Justin Leet wrot

[VOTE] Metron Release Candidate 0.5.0-RC2

Hi all, This is a call to vote on releasing Apache Metron 0.5.0 Full list of changes in this release: https://dist.apache.org/repos/dist/dev/metron/0.5.0-RC2/CHANGES The tag/commit to be voted upon is: (apache/metron) apache-metron-0.5.0-rc2 The source archive being voted upon can be found

Re: [VOTE] Metron Release Candidate 0.5.0-RC1

people to do? > > On Tue, May 29, 2018 at 11:30 AM Nick Allen wrote: > >> METRON-1544 was just merged into master. >> >> >> On Tue, May 29, 2018 at 2:16 PM, Justin Leet >> wrote: >> >> > I'm going to go ahead and cancel RC1, since METRON

Re: [VOTE] Metron Release Candidate 0.5.0-RC1

I'm going to go ahead and cancel RC1, since METRON-1544 looks pretty set. A new release candidate will be cut. Results (including my own vote): +1 Nick Allen -1 Otto Fowler Justin Leet On Tue, May 29, 2018 at 10:39 AM, Justin Leet wrote: > I didn't realize METRON-1544 wasn't in.

Re: [VOTE] Metron Release Candidate 0.5.0-RC1

, and spun-up the CentOS > > dev > > > environment successfully. > > > > > > > > > > > > On Fri, May 25, 2018 at 1:40 PM, Nick Allen > wrote: > > > > > > > This release does not contain an updated Bro plugin so

Bro plugin release process docs?

At the risk of exposing my ignorance, do we have the bro plugin release process documented anywhere? We have a doc for the main release ( https://cwiki.apache.org/confluence/display/METRON/Release+Process), but I haven't noticed one for the bro plugin. For the current RC, it's not included and

Re: [DISCUSS] Metron 0.5.0 Release Status Update

<n...@nickallen.org> wrote: > METRON-1565 was merged into master, but not updated for 0.5.0. I just > fixed that. > > https://issues.apache.org/jira/browse/METRON-1565 > > > > On Tue, May 22, 2018 at 8:28 PM, Justin Leet <justinjl...@gmail.com> > wrote: >

[DISCUSS] Metron 0.5.0 Release Status Update

Hi all, I'm working on kicking off our release process . As you might have seen today, a large number of tickets have been updated, in particular aligning things like Assignee, Status, and Fix Version. Please see Metron Jira -

Re: [DISCUSS] Metron release 0.5.0

On Tue, May 15, 2018 at 4:26 PM, Justin Leet <justinjl...@gmail.com> wrote: > Hi all, > > Based on a thread from last week > <https://lists.apache.org/thread.html/8e795ad4faecb4256f1cfa36ddbf757c9ef9b3d104eab9df6573d9a4@%3Cdev.metron.apache.org%3E>, > I'll be taking over as

[DISCUSS] Metron release 0.5.0

Hi all, Based on a thread from last week , I'll be taking over as the release manager for our next release. Thanks again to Matt for his work shepherding our previous

Re: [DISCUSS] Release Manager

I'd be happy to to volunteer to take over for a while. Thanks to Matt for all the help through the last couple releases! Justin On Thu, May 10, 2018 at 11:06 AM, Casey Stella wrote: > Hi All, > > Matt Foley, our esteemed Release manager for the last couple releases, has >

Re: [DISCUSS] Metron RPM spec changelog

changed, though. > > > > > > On Wed, Apr 18, 2018 at 9:47 AM Michael Miklavcic < > > > michael.miklav...@gmail.com> wrote: > > > > > > > We discovered yesterday while reviewing a PR that the RPM changelog > > > hasn't > > > &g

Re: [DISCUSS] Metron debug info tool

First off, this is super nice, and a great way to let us be able to debug and help others debug quickly, easily, and hopefully more consistently. I super briefly glanced at at it, so these might already be there, but I'd like to be able to filter what I get back, e.g. if I give the options for

Re: Apache Website Required Links

Whimsy has run the site checks since then, and unfortunately we're still showing that the links are missing. Like I said, I think it's because the links aren't actually on the homepage itself. On Thu, Feb 15, 2018 at 5:02 PM, Justin Leet <justinjl...@gmail.com> wrote: > Hey, I to

Re: Apache Website Required Links

ot;image": null, > > "thanks": "https://www.apache.org/foundation/thanks.html;, > > "copyparent": true > > } > > } > > On Thu, Feb 15, 2018 at 3:38 PM, Casey Stella <ceste...@gmail.com> wrote: > Just re

Apache Website Required Links

I'd created a Jira awhile ago, but it deserves a callout to the community. Especially if someone wants to grab it, it's probably something pretty easy (and valuable!) to do. There's a set of required links on Apache web pages, which can be seen at Website Navigation Links Policy

Re: [DISCUSS] Move SHELL type functions from management to stellar common

Agreed, I think it makes sense to move them there. On Wed, Jan 31, 2018 at 9:28 AM, Casey Stella wrote: > I'd be in favor of that. That is general purpose stuff. > > On Wed, Jan 31, 2018 at 9:12 AM, Otto Fowler > wrote: > > > Per:

[DISCUSS] Upgrading Solr

Now that we have ES at a modern version, we should consider bringing Solr to a modern version as well. The focus of this work would be to get us in a place where Solr is upgraded, along with the related work of building out the Solr functionality to parity with Elasticsearch. The goal would not

Re: Checkstyle - have we run it?

is the only feasible way is it not? > > > On January 17, 2018 at 12:15:33, Justin Leet (justinjl...@gmail.com) > wrote: > > It exists, we have a style that can be imported and setup in IntelliJ with > the Checkstyle plugin > > Reformatting can also be done in IntelliJ (which will

Re: Checkstyle - have we run it?

It exists, we have a style that can be imported and setup in IntelliJ with the Checkstyle plugin Reformatting can also be done in IntelliJ (which will help a lot, but not all issues). This can be done on a file mask basis (e.g. just do "*.java" files to avoid reformatting other things), and could

Re: [DISCUSS] Generating and Interacting with serialized summary objects

I agree with the general sentiment that we can tailor specific use cases via UI, and I'm worried that the use case specific solution (particularly in light of the note that it's not even general to the class of bloom filter problems, let alone an actually general problem) becomes more work than

Re: [DISCUSS] Removing Markdown files from rat exclusion

The PR is merged into master, and all relevant PRs have a comment noting that adding the header is required. As a reminder, this means Apache headers are required on all markdown files and this will be enforced by rat. On Sat, Dec 30, 2017 at 8:33 AM, Justin Leet <justinjl...@gmail.com>

Re: [DISCUSS] Removing Markdown files from rat exclusion

headers will be enforced properly going forwad. On Sun, Dec 24, 2017 at 8:09 PM, Justin Leet <justinjl...@gmail.com> wrote: > I'm gonna let this percolate until Wednesday or so, assuming conversation > doesn't reach a natural tipping point. I'm inclined to agree with Nick, > but I

Re: [DISCUSS] Removing Markdown files from rat exclusion

with master before they go in. > > > > On Sat, Dec 23, 2017 at 11:08 AM, Justin Leet <justinjl...@gmail.com> > wrote: > > > I have a PR currently out (https://github.com/apache/metron/pull/883) > that > > removes the rat exclusion on Markdown files. There was a d

Re: [VOTE] Metron Release Candidate 0.4.2-RC2

+1 validated with Otto's script * Checksums * Signatures * Build * Tests On Tue, Dec 19, 2017 at 11:47 PM, Anand Subramanian < asubraman...@hortonworks.com> wrote: > > * mvn clean package at root level > * mvn clean package -Pbuild-rpms at metron-deployment level and generate > RPMs > * Brought

[DISCUSS] Lowering the barrier to entry to for new users

One of the topics that came up in recent community meeting was about lowering the barrier to entry for new users. This is a fairly broad topic that I think covers a few different subtopics. 1) Addressing (or making it easier to address) some of the things we've seen on the user group from people

Re: [DISCUSS] Support Ubuntu Installs in the MPack

Yeah, I definitely agree with folding testing Ubuntu into an RC. It would be nice if we could fold that testing into a schedule, e.g. weekly, to avoid unpleasant surprises at RC time. Not really sure what the best way to go about that would be. I think a Jira on the testing topic is a good idea.

Re: [DISCUSS] Support Ubuntu Installs in the MPack

By 'direct support" I just meant that it becomes an installation target we semi-actively maintain a specific installation method for. Right now we don't need to communicate that all because we don't provide anything other RPMs. The cutoff is implicit: There's convenience RPMs you can build, or

Re: [DISCUSS] Stellar Documentation Autogeneration

tion’s should have it’s own > > > documentation. As part of breaking stellar out to it’s own module > > > we should remove stellar documentation from stellar common that > applies > > to > > > functions outside that module. > > >

Re: [DISCUSS] Support Ubuntu Installs in the MPack

If we start adding direct support for systems other than CentOS (which I'm in favor of), I suggest we make sure to very explicitly document what the level of support, testing, etc. for everything is. If we're not requiring everything to be tested against Ubuntu, we should make sure to document

[DISCUSS] Stellar Documentation Autogeneration

I think it would be valuable to have the documentation around Stellar being autogenerated. We have most of the info we'd want in the @Stellar annotation, and ideally, we could just pull this info out and produce some docs similar to what we already manually maintain. This came up a bit in the

Re: [DISCUSS] Integration/e2e test infrastructure requirements

I think this covers the main things I want to see from a first cut (which shouldn't be surprising to anyone who followed the PR thread). The potential follow-on I'd like to see, is having the integration + e2e tests handled during the maven integration test phase with the failsafe plugin, instead

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

Do we have any further discussion on this? Pardon me if I misstate anyone's position, but it seems like we have a couple people (Otto and Jon and slightly Matt?) in favor of (a), Nick in favor of (b), and presumably a section of people like myself without a particular horse in the race. It seems

Re: [DISCUSS] e2e test infrastructure

As an additional consideration, it would be really nice to get our current set of integration tests to be able to be run on this infrastructure as well. Or at least able to be converted in a known manner. Eventually, we could probably split out the integration tests from the unit tests entirely.

Re: MASTER is Broken

Casey's PR has been committed into master. Please update any branches/PRs as needed. On Wed, Oct 25, 2017 at 3:56 PM, Casey Stella <ceste...@gmail.com> wrote: > I expect that can be done via an infra request. Not sure though. > > On Wed, Oct 25, 2017 at 3:33 PM, Justin

Re: MASTER is Broken

To hop onto Otto's comment, it would be really nice to have master build failures go to the dev list. I have no idea who has permissions to set that up though, so if anyone does that'd be super helpful. On Wed, Oct 25, 2017 at 3:14 PM, Casey Stella wrote: > I noticed it on

Re: Master build failures in Travis

One last thing, I'd recommend that master get merged into everyone's branches/PRs to make sure the tests work consistently during any necessary Travis runs. On Wed, Oct 25, 2017 at 9:29 AM, Justin Leet <justinjl...@gmail.com> wrote: > Master is building again! Thanks to Ryan for ta

Master build failures in Travis

See: METRON-1274 and https://travis-ci.org/apache/metron/builds An example failure is https://travis-ci.org/apache/metron/builds/290806887 This is possibly intermittent and possibly a result of METRON-1241

Re: [DISCUSS] Release Process Update

I'd argue it shouldn't be in the site-book at all. Presumably we aren't releasing while Travis is broken, so it's not useful information for anyone looking at docs. It just carries over from the main README. Seems like we should just scrub it when we do the other fixes to the READMEs to make them

Re: Cloudtrail use case

t; > However Laurens wants to write it up will work. If you type it up, throw > it > > in an envelope, seal it with a stamp, and physically mail it to me, I > will > > make sure it lands in the right place. :) > > > > > > > > On Thu, Oct 5, 2017 at 9

Re: Quick Dev

, Oct 6, 2017 at 8:46 AM, Nick Allen <n...@nickallen.org> wrote: > The same case might be made for the Code Lab Platform > `metron-deployment/vagrant/codelab-platform`? > > On Fri, Oct 6, 2017 at 8:44 AM Justin Leet <justinjl...@gmail.com> wrote: > > > Wiki up

Re: Quick Dev

we can reduce that surface area, life will be a lot > > easier on the user list. > > > > > On 6 Oct 2017, at 13:28, zeo...@gmail.com <zeo...@gmail.com> wrote: > > > > > > I say we kill it and repoint the site. That will give us one less > thing > >

Quick Dev

So what are we going to do with Quick Dev? I'm pretty sure everybody's been using full dev for awhile now (and quick dev is probably broken since I'm sure we haven't been regularly updating it). I just realized our website links to a wiki page that says to use quick dev. Given that quick dev is

Re: Cloudtrail use case

I know we've had discussions about migrating stuff into docs before. It might be worth resurrecting a more use case focused version of that, instead of starting on the wiki. I assume the end goal is availability in the site-book, so even if it's not in a perfect place, I'd rather the effort be

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

Do we intend on (or have interest in) supporting ES across major version for a given version of Metron? I'm not convinced it's worth the work of using the low level client. This really only seems useful for ES clusters that are being used outside Metron and need to be on a different ES major

Re: [DISCUSS] Dropping support for elastic 2.x

Forgot the link https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-upgrade.html On Wed, Oct 4, 2017 at 1:07 PM, Simon Elliston Ball < si...@simonellistonball.com> wrote: > The simplest option would probably be to upgrade the ES and then reindex > from the HDFS store.

Re: [DISCUSS] Dropping support for elastic 2.x

ES should be upgradeable without wiping. It's the client itself that isn't backwards compatible. It'll require both an upgrade of Metron and an ES cluster. On Wed, Oct 4, 2017 at 1:05 PM, Casey Stella wrote: > So, how would this work in an upgrade scenario that does not

Re: [DISCUSS] Meta alert Elasticsearch new template requirement ramifications

. On Fri, Sep 29, 2017 at 10:10 AM, Otto Fowler <ottobackwa...@gmail.com> wrote: > We can also consider this when thinking about creating parsers with > archetypes that contain ‘default’ > elasticsearch templates. > > > > On September 29, 2017 at 10:00:03, Justin

[DISCUSS] Meta alert Elasticsearch new template requirement ramifications

As part of building a backend for meta-alerts ( https://github.com/apache/metron/pull/734), there's an additional requirement for the Elasticsearch templates for new sensors. Although seemingly minor, this should be called out explicitly because of the wider implications of leaving it out of ANY

Re: [DISCUSS] Code Reformatting next steps

; and blank line after license block). > All of us with open PRs will then have to update to master, but we do that > periodically anyway. Github is really quite good about not causing extra > review work for update merges. > IMHO, > --Matt > > On 8/11/17, 5:14 AM, "Jus

Re: [DISCUSS] Code Reformatting next steps

t not causing extra > review work for update merges. > IMHO, > --Matt > > On 8/11/17, 5:14 AM, "Justin Leet" <justinjl...@gmail.com> wrote: > > Now that METRON-746 <https://github.com/apache/metron/pull/577> is in, we > have a consistent code formattin

Re: Metron Alerts bombing in Travis?

I just merged Raghu's PR into master, so we should be good to go. On Fri, Aug 11, 2017 at 12:53 PM, Justin Leet <justinjl...@gmail.com> wrote: > I disagree with the hardcoded versions being bad, the obvious concern I > have being the repeatability of the build. > > I'd also li

Re: Metron Alerts bombing in Travis?

) > > discussion on changing the dependency tool set and discuss pros and cons. > > > > On Fri, Aug 11, 2017 at 10:45 AM Justin Leet <justinjl...@gmail.com> > > wrote: > > > > > I'm honestly not very familiar with this stuff, but this seems more > lik

Re: Metron Alerts bombing in Travis?

I'm honestly not very familiar with this stuff, but this seems more like a "how we use it issue", rather than an issue with the tech itself. Do we have a more compelling reason, or set of reasons, beyond just fixing to specific version of our dependencies? On Fri, Aug 11, 2017 at 10:37 AM, Nick

Re: [DISCUSS] Code Reformatting next steps

template about this. Did we change the > contributor’s guide? > > Also, are there common steps to take with Intellij, so that we all do the > same thing > for mass reformats? > > On August 11, 2017 at 08:14:21, Justin Leet (justinjl...@gmail.com) wrote: > > Now that M

[DISCUSS] Code Reformatting next steps

Now that METRON-746 is in, we have a consistent code formatting setup where (for the most part) it can be autoapplied. Barring one existing PR, the main thing is just picking a module, doing the format, and testing it out. Obviously, I'd like to avoid

Re: MaaS and Metron Architecture talks at DataWorks Summit SJ 2017

Could we put these up on the wiki page for tech talks in the community? That page could probably use some love, although I know we've had discussions about what we should do with wiki content. https://cwiki.apache.org/confluence/display/METRON/Tech+Talks On Thu, Aug 3, 2017 at 10:32 AM, Casey

Re: Java Code style is now Google Java Style Guide

The wiki at Development Guidelines <https://cwiki.apache.org/confluence/display/METRON/Development+Guidelines> has been updated, please take a look and if any updates are required, feel free to reply and I'll update the page. Justin On Mon, Jul 31, 2017 at 10:23 PM, Justin Leet <

Java Code style is now Google Java Style Guide

Hi all, Following the merge of METRON-746 in https://github.com/apache/metron/pull/577, our code style is to follow the Google Java Style Guide , where previously it was a two-space indented

Re: Code style change requires vote?

during discussion / vote? Obviously, this is moot if the answer is we don't need a vote since that PR did have the appropriate +1's. At that point, I'd send an email calling it out and make the appropriate wiki changes for getting people setup. On Mon, Jul 31, 2017 at 1:50 PM, Justin Leet

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

;> my 2c. >> >> On Fri, Jul 28, 2017 at 11:51 AM, Otto Fowler <ottobackwa...@gmail.com> >> wrote: >> >> > +1 for CONTRIBUTING.md >> > >> > >> > On July 28, 2017 at 09:14:38, Justin Leet (justinjl...@gmail.com) >> wrot

Re: ability to submit patches

Hi Artem, We do our patches and reviews via pull requests on GitHub ( https://github.com/apache/metron) If you aren't familiar with the GitHub PR process, take a look at https://help.github.com/articles/creating-a-pull-request-from-a-fork/ Let us know if there's anything in particular you need

UI pivotting / aggregation backend

I wanted to bring up a some stuff on the backend of our UI, and get thoughts (+ things I overlooked, etc.). There's also a couple points at the end that merit discussion about how we handle things, since it gets into how we handle our ES templates (since we generally want to aggregate on raw

Re: [ANNOUNCE] Apache Metron 0.4.0 release

Congrats, everyone! A lot of people helped out across the board, and I look forward to everyone's contributions moving ahead. On Wed, Jul 5, 2017 at 4:47 PM, Otto Fowler wrote: > Thank you Matt, your first metron release as well! > Congratulations to the community. > >

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

Looks like it's already been closed, with a5b1377 as the latest commit. We should be good to go at this point. Any objections, Matt? On Mon, Jul 3, 2017 at 2:39 PM, Matt Foley wrote: > https://issues.apache.org/jira/browse/INFRA-14502 has been opened. > > On 7/3/17,

METRON-1004 Build improvements are in master

METRON-1004 was made to address several issues we were having with the Travis builds. Specifically that the builds went on too long. After the merge into master, builds should be more consistent, stable, and take about 25-30 minutes. Please merge master into PRs if you are experiencing issues

Re: [VOTE] Apache Metron 0.4.0 release

+1 (Non-binding) * Verified Keys * Verified mvn clean install completed successfully * Ran full dev: saw data flow through, ran a couple of the REST APIs, and opened up and clicked through a bit of the Management API. * Examined site-book and didn't see any issues On Thu, Jun 29, 2017 at 11:46

Re: [DISCUSS] Mutation of Indexed Data

5f0d3309>, > right? It provides a single key for a given message that globally stored > with the message, regardless of where/how. > > Jon > > On Thu, Jun 22, 2017 at 9:01 AM Justin Leet <justinjl...@gmail.com> wrote: > > > First off, I agree with the characteristi

Re: [DISCUSS] Mutation of Indexed Data

First off, I agree with the characteristics. For the data stores, we'll need to be able to make sure we can actually handle the collapsing of the updates into a single view. Casey mentioned making the long term stores transparent, but there's potentially work for the near real time stores: we

Re: METRON-777

I know I'd like people (probably myself included) to start digging in. I'm in a bit of the same boat where I'll have to do some work (a lot?) to familiarize myself better with everything to properly review it, but hopefully if we have a few sets of eyes looking at it we'll get everything squared

Re: [DISCUSS] Code Style

;ma...@apache.org> wrote: > Could I ask please that any major reformat wait until the Metron 0.4.0 > release is out? > Such across-the-board changes usually induce instability for a while, no > matter how carefully done. > > Thanks, > --Matt > (with RM hat on) > &

Re: [DISCUSS] Code Style

exactly how we want it to work (e.g. handling just avoiding introducing new errors vs just not allowing any errors vs. setting max errors per module). I'm not sure how other projects handle this, and we probably want to look into it. On Tue, May 9, 2017 at 6:07 AM, Justin Leet <justinjl...@gmail.

Re: Site-Book: mvn site never completes

Just merged it On Tue, May 9, 2017 at 4:26 PM, Otto Fowler <ottobackwa...@gmail.com> wrote: > Who is going to merge this? > > > On May 9, 2017 at 15:21:07, Justin Leet (justinjl...@gmail.com) wrote: > > https://github.com/apache/incubator-metron/pull/575 > > Somewh

Re: Site-Book: mvn site never completes

take 1.3 seconds to parse." On Tue, May 9, 2017 at 11:34 AM, Justin Leet <justinjl...@gmail.com> wrote: > https://github.com/apache/incubator-metron/blob/ > 716bda326f26b60c98318cdc1cc949b351a0b71a/metron-interface/ > metron-rest/README.md appears to be the problem. I can ru

Re: Site-Book: mvn site never completes [MASTER BROKEN?]

because of the time involved). We should be able to use maven.javadoc.skip to do that, but I'd have to test it first. On Tue, May 9, 2017 at 1:50 PM, Otto Fowler <ottobackwa...@gmail.com> wrote: > So, is the build considered broken or what? > > > On May 9, 2017 at 11:34:23, Jus

Re: Site-Book: mvn site never completes

https://github.com/apache/incubator-metron/blob/716bda326f26b60c98318cdc1cc949b351a0b71a/metron-interface/metron-rest/README.md appears to be the problem. I can run the site successfully on the commit before, and this commit hangs. Just glancing through, the file appears fine on Github, but

Re: [DISCUSS] Code Style

> 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" <kylerichards...@gmail.com> > wrote: > > > &g

Re: [DISCUSS] Code Style

through how to do it) as part of the exercise. On Mon, May 8, 2017 at 9:40 AM, Otto Fowler <ottobackwa...@gmail.com> wrote: > +1. > Does anyone have an idea setup for this? > > > On May 8, 2017 at 09:29:15, Justin Leet (justinjl...@gmail.com) wrote: > > I've been

[DISCUSS] Code Style

I've been taking a look at setting up checkstyle per https://issues.apache.org/jira/browse/METRON-746. Given that we don't actually enforce any style right now (saying we use Sun's is not the same as enforcing it!), and plan to do a blanket format after we get checkstyle setup, this seems like a

Re: Error building in Travis after taking master

, 2017 at 14:04:32, Otto Fowler (ottobackwa...@gmail.com) wrote: > > > git checkout -b whyyounowork apache/master > > same issue locally > > > > > On May 3, 2017 at 13:46:14, Justin Leet (justinjl...@gmail.com) wrote: > > Is it just that one branch that's fa

Re: Error building in Travis after taking master

vn package > > I’m trying it now. > > > On May 3, 2017 at 12:19:34, Michael Miklavcic (michael.miklav...@gmail.com > ) > wrote: > > Also Otto, are you able to build locally with that branch and same merge > with master? > > On Wed, May 3, 2017 at 9:51 AM, Justin Leet <

Re: Recent commit without JIRA in commit message

To add some context, the problem here is that when I squashed METRON-799 it became 3 commits, in order to keep proper attribution. I missed having the jira on the last of the 3 commits during the squash. The other two commits do still have it: commit 41b5b1050cf29e5dcb5d0c36b5a9dbd1cafa745e

Re: [DISCUSS] Regression introduced in Full Dev

The problem seems to be that full/quick dev rely on having the RPMs in the /target folder >From metron-deployment/roles/metron-rpms/defaults: metron_rpm_glob: "{{ playbook_dir }}/../packaging/docker/rpm-docker/target/RPMS/noarch/*.rpm" However, that PR appears to no longer copy to the /target

<    1   2   3   >