[GitHub] incubator-metron issue #400: METRON-636: Capture memory and cpu details as a...

Github user anandsubbu commented on the issue: https://github.com/apache/incubator-metron/pull/400 For all other OS types other than `darwin` and` linux`, I have added a generic log message. Please let me know if there is any other change required at this point. --- If your project

[PROPOSAL] Metron Community

Right now we have 2 entries for Metron Community. One on our Wiki, which I think is outdated and should be removed as it no longer offers value. The second is on our website, which is up to date. So I am proposing we remove the wiki entry. ---  Thank you, James Sirota

[GitHub] incubator-metron issue #399: METRON-600: Fix Metron Website

Github user james-sirota commented on the issue: https://github.com/apache/incubator-metron/pull/399 @mattf-horton does this adequately meet your concerns? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project

Re: [VOTE] Reporting Issues Wiki

Can I get some more votes on this so I can close it out? 10.01.2017, 13:50, "Ryan Merriman" : > +1 (binding) > > On Mon, Jan 9, 2017 at 8:23 AM, Casey Stella wrote: > >>  +1 (binding) >> >>  On Fri, Jan 6, 2017 at 7:43 PM, Kyle Richardson

Re: [DISCUSS] Release Process

Ok. just made the last of the changes. Putting it up for a vote... Thanks for your comments, guys. James 17.01.2017, 15:17, "Matt Foley" : > Sure, sounds fine to me. > > On 1/17/17, 1:03 PM, "Casey Stella" wrote: > > We haven't actually bitten off

Re: [DISCUSS] Release Process

Sure, sounds fine to me. On 1/17/17, 1:03 PM, "Casey Stella" wrote: We haven't actually bitten off the "publishing maven artifacts" just yet, so I can't say that I have a good idea in my head what the detailed steps are going to be. If we think that it's a good

Re: [DISCUSS] Hosting Kraken maven artifacts in incubator-metron git repo

On Fri, Jan 13, 2017 at 3:35 PM, Matt Foley wrote: > Perhaps it would be more appropriate to put it under > https://dist.apache.org/repos/dist/release/incubator/metron/ , perhaps as > https://dist.apache.org/repos/dist/release/incubator/metron/mvn-repo ? > No, we could only do

Re: [DISCUSS] Release Process

That looks great, Casey! Gonna save this off for addressing the same in Knox if needed. :) On Tue, Jan 17, 2017 at 3:33 PM, Casey Stella wrote: > Larry, > > Thanks for the info. In that case, then the following passage: > > > Now, we must grab the release candidate binary

Re: [MENTORS] Questions about Release Process

A release is a release, even if it is urgent. So, yes, the normal release process still applies. To expedite, you can shorten the typical 72 hour turnaround, but you still want at least 3 positive votes. -Taylor > On Jan 17, 2017, at 3:06 PM, Casey Stella wrote: > >

[GitHub] incubator-metron issue #397: METRON-627: Add HyperLogLogPlus implementation ...

Github user mmiklavc commented on the issue: https://github.com/apache/incubator-metron/pull/397 Merged with latest master and modified Stellar.g4 to handle EOL fragments. Test went from failing to passing locally. --- If your project is set up for it, you can reply to this email

Re: [DISCUSS] Release Process

It is technically a violation of apache release policy to build releases in such a way [1]: MUST RELEASES BE BUILT ON HARDWARE OWNED AND CONTROLLED BY THE COMMITTER? Strictly speaking, releases must be verified

Re: [DISCUSS] Release Process

Speaking as the current release manager, it's pretty obvious when you've done something wrong and as part of the vote in incubator general the collateral is pretty heavily scrutinized. On Mon, Jan 16, 2017 at 3:52 PM, Otto Fowler wrote: > If you are the person

Re: Pittsburgh PA Meetup

Great job! Thank you for presentation and recording. They are really important for me who live away. Greetings from Turkey. Hakan Akansel On Tue, Jan 17, 2017 at 10:37 PM, Houshang Livian wrote: > Really great presentation Jon. Go to minute 31 to get right to the

Re: [DISCUSS] Release Process

Hey Matt, Github actually constructs the tarball for us using git archive (for every tag, for that matter). We don't explicitly push any tarball to github. The reason why we pull the tarball from github directly is that we ship a .gitattributes to define what gets put in the tarball. (we don't

Re: Pittsburgh PA Meetup

Really great presentation Jon. Go to minute 31 to get right to the Metron conversation On 1/17/17, 11:32 AM, "James Sirota" wrote: >Great Job Jon! > >Will watch the recording tonight > >James > >17.01.2017, 11:55, "zeo...@gmail.com" : >> By the way I

Re: Pittsburgh PA Meetup

Great Job Jon! Will watch the recording tonight James 17.01.2017, 11:55, "zeo...@gmail.com" : > By the way I had this event – there were about 70 attendees. Here is the > fallout (posted here > >

Re: Pittsburgh PA Meetup

By the way I had this event – there were about 70 attendees. Here is the fallout (posted here behind a login page): Recording Presentation Slides

[GitHub] incubator-metron issue #397: METRON-627: Add HyperLogLogPlus implementation ...

Github user mmiklavc commented on the issue: https://github.com/apache/incubator-metron/pull/397 Ok, this is making more sense now. GitHub has merged this PR out of band of the build. That fetch is not doing a merge. It's fetching what has already been merged out of band from the

[GitHub] incubator-metron issue #397: METRON-627: Add HyperLogLogPlus implementation ...

Github user jjmeyer0 commented on the issue: https://github.com/apache/incubator-metron/pull/397 @mmiklavc have you rebased lately? If not, I'm sure the PR I submitted for Stellar comparisons is the culprit. --- If your project is set up for it, you can reply to this email and have

[GitHub] incubator-metron issue #397: METRON-627: Add HyperLogLogPlus implementation ...

Github user cestella commented on the issue: https://github.com/apache/incubator-metron/pull/397 @jjmeyer0 Makes sense and that explains things. @mmiklavc despite it being out of the scope of this ticket, it should just be a 1-liner and we should probably correct it as part of this

Re: [PROPOSAL] Reduce Reliance on Ansible for Deployment

+1, great you’re addressing this! On 1/17/17, 7:34 AM, "David Lyle" wrote: In our "Dev Guide and Committer Review Guide additions" discussion, we had a bit of a side discussion about reducing reliance (perhaps to zero) on Ansible for our installation.

[GitHub] incubator-metron issue #397: METRON-627: Add HyperLogLogPlus implementation ...

Github user jjmeyer0 commented on the issue: https://github.com/apache/incubator-metron/pull/397 Okay, I took a look. It's because EOL isn't defined as a fragment. If `EOL : '\n';` is changed to `fragment EOL : '\n';` it should work. Without the `fragment` keyword antlr4

[GitHub] incubator-metron issue #397: METRON-627: Add HyperLogLogPlus implementation ...

Github user cestella commented on the issue: https://github.com/apache/incubator-metron/pull/397 @jjmeyer0 @mmiklavc It appears that a regression was added relatively recently that affects whitespace at the end of stellar rules (the whitespace isn't sent to the skip channel in the

[GitHub] incubator-metron issue #397: METRON-627: Add HyperLogLogPlus implementation ...

Github user mmiklavc commented on the issue: https://github.com/apache/incubator-metron/pull/397 @dlyle65535 the thing I'm not fully understanding is how this is working in my local branch. Doing a git fetch and checkout shouldn't merge anything from master, so the most recent master

[GitHub] incubator-metron issue #397: METRON-627: Add HyperLogLogPlus implementation ...

Github user jjmeyer0 commented on the issue: https://github.com/apache/incubator-metron/pull/397 This looks like an issue with the grammar. My guess is it isn't properly handling white space at the end. If you change the variable `hllpDefaultConstructorRule` to the below, it should

[GitHub] incubator-metron pull request #418: METRON-666 Fix javadoc doclint errors

GitHub user mattf-horton reopened a pull request: https://github.com/apache/incubator-metron/pull/418 METRON-666 Fix javadoc doclint errors Fixes for Java 8 javadocs automatic doclint problems: - replaced many uses of `` and `` with simple uses of `` - wrapped uses of `<` or

[GitHub] incubator-metron issue #418: METRON-666 Fix javadoc doclint errors

Github user mattf-horton commented on the issue: https://github.com/apache/incubator-metron/pull/418 Kicking Travis. Bad Travis! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature

[GitHub] incubator-metron pull request #418: METRON-666 Fix javadoc doclint errors

Github user mattf-horton closed the pull request at: https://github.com/apache/incubator-metron/pull/418 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if

[GitHub] incubator-metron issue #397: METRON-627: Add HyperLogLogPlus implementation ...

Github user dlyle65535 commented on the issue: https://github.com/apache/incubator-metron/pull/397 I was able to duplicate the failures in my environment by doing the following (based on what Travis does). ``` mkdir mike_test cd mike_test git clone --depth=50

[GitHub] incubator-metron issue #397: METRON-627: Add HyperLogLogPlus implementation ...

Github user mmiklavc commented on the issue: https://github.com/apache/incubator-metron/pull/397 Hm, something fishy going on here with Travis. Running all tests fine from Maven (on OSX) locally. ``` [INFO] metron-analytics ... SUCCESS [ 1.079

Re: [PROPOSAL] Reduce Reliance on Ansible for Deployment

Ambari exposes templating via configs and parameter classes. The current configuration screens for Metron Enrichment is a pretty good example of that, they fill in templates under the covers. -D... On Tue, Jan 17, 2017 at 11:55 AM, Nick Allen wrote: > Plan sounds solid. >

Re: [PROPOSAL] Reduce Reliance on Ansible for Deployment

Plan sounds solid. I've been curious how to replicate the templating that Ansible gives us. Do we have a plan for that or is that something we have to figure out? On Tue, Jan 17, 2017 at 10:34 AM, David Lyle wrote: > In our "Dev Guide and Committer Review Guide additions"

[GitHub] incubator-metron issue #418: METRON-666 Fix javadoc doclint errors

Github user cestella commented on the issue: https://github.com/apache/incubator-metron/pull/418 @nickwallen That would be one way to fix it, for sure. I did bump the timeout a bit in #415, but it might could stand more. --- If your project is set up for it, you can reply to this

[GitHub] incubator-metron issue #418: METRON-666 Fix javadoc doclint errors

Github user cestella commented on the issue: https://github.com/apache/incubator-metron/pull/418 @nickwallen replied on the dev list. Replicating here for posterity: @nickwallen said: This is a self-imposed limit, no? See ComponentRunner.java:131. Do we just need to give

[GitHub] incubator-metron issue #418: METRON-666 Fix javadoc doclint errors

Github user cestella commented on the issue: https://github.com/apache/incubator-metron/pull/418 @jjmeyer0 It's timeouts in the test itself, so parallel execution wouldn't really help (this particular test sends data through and waits til it gets written out). --- If your project

[GitHub] incubator-metron issue #418: METRON-666 Fix javadoc doclint errors

Github user cestella commented on the issue: https://github.com/apache/incubator-metron/pull/418 So, one comment here for posterity and to make sure we're all on the same page. This error started happening yesterday to my PR (#417). Here's what happened: * @mmiklavc asked for a

Re: [GitHub] incubator-metron issue #418: METRON-666 Fix javadoc doclint errors

> > Tests in error: > test(org.apache.metron.solr.integration.SolrIndexingIntegrationTest): Took > too long to complete: 150963 > 15 This is a self-imposed limit, no? See ComponentRunner.java:131. Do we just need to give Travis some more time? On Tue, Jan 17, 2017 at 10:05 AM, JJ Meyer

Re: [GitHub] incubator-metron issue #418: METRON-666 Fix javadoc doclint errors

How does Maven split tasks up these tasks? My only concern there is that we have some robust integration test infrastructure data setup that may not be thread-safe. On Tue, Jan 17, 2017 at 7:55 AM, jjmeyer0 wrote: > Github user jjmeyer0 commented on the issue: > >

[GitHub] incubator-metron issue #418: METRON-666 Fix javadoc doclint errors

Github user JonZeolla commented on the issue: https://github.com/apache/incubator-metron/pull/418 Yeah, it looks like the latest master build failed as well. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your

[GitHub] incubator-metron issue #418: METRON-666 Fix javadoc doclint errors

Github user cestella commented on the issue: https://github.com/apache/incubator-metron/pull/418 I'd kick travis by closing and reopening this PR. I think this has to do with Travis being overloaded so the test is timing out. --- If your project is set up for it, you can reply to

[GitHub] incubator-metron pull request #418: METRON-666 Fix javadoc doclint errors

GitHub user mattf-horton opened a pull request: https://github.com/apache/incubator-metron/pull/418 METRON-666 Fix javadoc doclint errors Fixes for Java 8 javadocs automatic doclint problems: - replaced many uses of `` and `` with simple uses of `` - wrapped uses of `<` or