[jira] [Created] (METRON-1021) increment metron version number to 0.4.1 in poms

[Matt Foley (JIRA)]

Matt Foley created METRON-1021:
--

 Summary: increment metron version number to 0.4.1 in poms
 Key: METRON-1021
 URL: https://issues.apache.org/jira/browse/METRON-1021
 Project: Metron
  Issue Type: Task
Reporter: Matt Foley


It is good practice to increment the build version in POMs immediately after a 
release, so that builds with new stuff cannot be mistaken for builds of the 
release version. Consistent with METRON-1020 I suggest incrementing the minor 
rather than the major version number for now, before we know what we're going 
to release next and when.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (METRON-633) Create better logging for HbaseEnrichmentWriter

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075517#comment-16075517
 ] 

ASF GitHub Bot commented on METRON-633:
---

Github user zezutom commented on the issue:

https://github.com/apache/metron/pull/572
  
@justinleet I can't merge this PR, do you mind merging to master yourself? 
Cheers.


> Create better logging for HbaseEnrichmentWriter
> ---
>
> Key: METRON-633
> URL: https://issues.apache.org/jira/browse/METRON-633
> Project: Metron
>  Issue Type: Bug
>Reporter: Casey Stella
>Assignee: Tomas Zezula
>  Labels: newbie
>
> Right now our debug logging is nonexistent for this writer and it makes 
> tracking down issues almost impossible.  This should be corrected. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (METRON-1008) Migrate Travis build to use Trusty

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075499#comment-16075499
 ] 

ASF GitHub Bot commented on METRON-1008:


Github user jjmeyer0 commented on the issue:

https://github.com/apache/metron/pull/633
  
Quote from @justinleet 
> I'd be inclined towards avoiding splitting the build if we were only 
getting a couple minutes out of it. I'm a little worried about being able to 
get three slots on the occasionally stretched Apache setup. Integration tests 
and building are the long poles in the tent, so splitting out the other tests 
doesn't really save us much time here, unfortunately.

I agree, I have reverted this.



Quote from @ottobackwards 
> I'm going to be honest. Now that we have the builds kind of working 
again, I'm a little hesitant to change them for anything but an absolute 
certainty of a return, that we completely understand.
> 
> I think the travis build strategy should be a longer living branch maybe.

I reverted the multiple env changes, as I agree, it's not worth the small 
chunk of time that was shaved off. However, I think the rest of these changes 
can be helpful for the following reasons:

* moving the license verification to an earlier step can help the build 
fail fast. Forgetting to update the dependency file can be a common mistake. 
Failing earlier might save time and travis resources.
* I believe moving to trusty was recommended by travis-ci
* using travis' install step for the `mvn install`. No benefit that I know 
of. I just believe `mvn install` should happen here.




> Migrate Travis build to use Trusty
> --
>
> Key: METRON-1008
> URL: https://issues.apache.org/jira/browse/METRON-1008
> Project: Metron
>  Issue Type: Bug
>Reporter: Justin Leet
>
> [~zeo...@gmail.com] pinged someone from Travis while we were working on 
> METRON-1004.  In addition to confirming that we should be using a VM, it was 
> also suggested we move to Trusty.  This was briefly looked at in during 
> METRON-1004, in particular because it (theoretically) has the correct version 
> of compilers installed, so we could avoid the hit of setting that up.  It 
> blew up on `npm install`, possibly from my own ignorance.
> At minimum we should move to Trusty:
> {code}
> https://docs.travis-ci.com/user/trusty-ci-environment/
> {code}
> Ideally, we do some more thorough investigation of the compiler and see if we 
> can cut out that step.
> See:
> https://docs.travis-ci.com/user/trusty-ci-environment/



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (METRON-1008) Migrate Travis build to use Trusty

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075484#comment-16075484
 ] 

ASF GitHub Bot commented on METRON-1008:


Github user jjmeyer0 commented on the issue:

https://github.com/apache/metron/pull/632
  
Unfortunately I will have to open a new PR. I squashed my commits when this 
PR was closed. Github doesn't allow to reopen PRs when force pushes occur when 
the PR is closed.  @justinleet and @ottobackwards I'll address your comments on 
the new PR.

My apologies, I was not aware of this. 


> Migrate Travis build to use Trusty
> --
>
> Key: METRON-1008
> URL: https://issues.apache.org/jira/browse/METRON-1008
> Project: Metron
>  Issue Type: Bug
>Reporter: Justin Leet
>
> [~zeo...@gmail.com] pinged someone from Travis while we were working on 
> METRON-1004.  In addition to confirming that we should be using a VM, it was 
> also suggested we move to Trusty.  This was briefly looked at in during 
> METRON-1004, in particular because it (theoretically) has the correct version 
> of compilers installed, so we could avoid the hit of setting that up.  It 
> blew up on `npm install`, possibly from my own ignorance.
> At minimum we should move to Trusty:
> {code}
> https://docs.travis-ci.com/user/trusty-ci-environment/
> {code}
> Ideally, we do some more thorough investigation of the compiler and see if we 
> can cut out that step.
> See:
> https://docs.travis-ci.com/user/trusty-ci-environment/



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (METRON-1020) minor changes to release process

[Matt Foley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/METRON-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Foley updated METRON-1020:
---
Description: 
The following proposed changes are not just editorial in nature, hence will 
request vote of the community to change.  Regarding the process at 
https://cwiki.apache.org/confluence/display/METRON/Release+Process :

* Add a step to tag the final release, as 
"apache-metron--release".

* The current policy says that when a critical release is urgently needed, "the 
72 hour waiting periods in Steps 7 and 8 can be waived."  The formerly 
referenced Step 8 was for the Incubator vote, so that can be removed as an 
editorial issue, but we should also allow for not waiting for mirror 
propagation -- let the mirrors catch up as fast as they can.  So the text 
should now read:  "the 72 hour waiting period in Step 7 and the wait for mirror 
propagation in Step 10 can be waived."

* Finally, it is good practice to increment the build version in POMs 
immediately AFTER a release, so that builds with new stuff cannot be mistaken 
for builds of the release version.  The current policy says to increment it 
just BEFORE a release.  I suggest changing this to say:
** immediately after a release, increment the MINOR version number (eg, with 
the 0.4.0 just released, set the new version number to 0.4.1)
** immediately before a release, decide whether it will be a minor or major 
release.  If minor, assure that the minor version number was already 
incremented after the last release and continue to use that number.  If major, 
change the version number to the desired new major version.
** These version number changes are in master branch.  Creation of new branches 
does not occur until the idea of creating a maintenance branch or a new release 
branch has been consented by the community.


  was:
The following proposed changes are not just editorial in nature, hence will 
request vote of the community to change.  Regarding the process at 
https://cwiki.apache.org/confluence/display/METRON/Release+Process :

* Add a step to tag the final release, as 
"apache-metron--release".

* The current policy says that when a critical release is urgently needed, "the 
72 hour waiting periods in Steps 7 and 8 can be waived."  The formerly 
referenced Step 8 was for the Incubator vote, so that can be removed as an 
editorial issue, but we should also allow for not waiting for mirror 
propagation -- let the mirrors catch up as fast as they can.  So the text 
should now read:  "the 72 hour waiting period in Step 7 and the wait for mirror 
propagation in Step 10 can be waived."

* Finally, it is good practice to increment the build version in POMs 
immediately AFTER a release, so that builds with new stuff cannot be mistaken 
for builds of the release version.  The current policy says to increment it 
just BEFORE a release.  I suggest changing this to say:
** immediately after a release, increment the MINOR version number (eg, with 
the 0.4.0 just released, set the new version number to 0.4.1)
** immediately before a release, decide whether it will be a minor or major 
release.  If minor, assure that the minor version number was already 
incremented after the last release and continue to use that number.  If major, 
change the version number to the desired new major version.



> minor changes to release process
> 
>
> Key: METRON-1020
> URL: https://issues.apache.org/jira/browse/METRON-1020
> Project: Metron
>  Issue Type: Improvement
>Reporter: Matt Foley
>
> The following proposed changes are not just editorial in nature, hence will 
> request vote of the community to change.  Regarding the process at 
> https://cwiki.apache.org/confluence/display/METRON/Release+Process :
> * Add a step to tag the final release, as 
> "apache-metron--release".
> * The current policy says that when a critical release is urgently needed, 
> "the 72 hour waiting periods in Steps 7 and 8 can be waived."  The formerly 
> referenced Step 8 was for the Incubator vote, so that can be removed as an 
> editorial issue, but we should also allow for not waiting for mirror 
> propagation -- let the mirrors catch up as fast as they can.  So the text 
> should now read:  "the 72 hour waiting period in Step 7 and the wait for 
> mirror propagation in Step 10 can be waived."
> * Finally, it is good practice to increment the build version in POMs 
> immediately AFTER a release, so that builds with new stuff cannot be mistaken 
> for builds of the release version.  The current policy says to increment it 
> just BEFORE a release.  I suggest changing this to say:
> ** immediately after a release, increment the MINOR version number (eg, with 
> the 0.4.0 just released, set the new version number to 0.4.1)
> ** immediately before a release, decide whether it will be a minor or 

[jira] [Created] (METRON-1020) minor changes to release process

[Matt Foley (JIRA)]

Matt Foley created METRON-1020:
--

 Summary: minor changes to release process
 Key: METRON-1020
 URL: https://issues.apache.org/jira/browse/METRON-1020
 Project: Metron
  Issue Type: Improvement
Reporter: Matt Foley


The following proposed changes are not just editorial in nature, hence will 
request vote of the community to change.  Regarding the process at 
https://cwiki.apache.org/confluence/display/METRON/Release+Process :
* Add a step to tag the final release, as "apache-metron--release"
* The current policy says that when a critical release is urgently needed, "the 
72 hour waiting periods in Steps 7 and 8 can be waived."  The formerly 
referenced Step 8 was for the Incubator vote, so that can be removed as an 
editorial issue, but we should also allow for not waiting for mirror 
propagation -- let the mirrors catch up as fast as they can.  So the text 
should now read:  "the 72 hour waiting period in Step 7 and the wait for mirror 
propagation in Step 10 can be waived."
* Finally, it is good practice to increment the build version in POMs 
immediately AFTER a release, so that builds with new stuff cannot be mistaken 
for builds of the release version.  The current policy says to increment it 
just BEFORE a release.  I suggest changing this to say:
** immediately after a release, increment the MINOR version number (eg, with 
the 0.4.0 just released, set the new version number to 0.4.1)
** immediately before a release, decide whether it will be a minor or major 
release.  If minor, assure that the minor version number was already 
incremented after the last release and continue to use that number.  If major, 
change the version number to the desired new major version.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (METRON-1008) Migrate Travis build to use Trusty

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075368#comment-16075368
 ] 

ASF GitHub Bot commented on METRON-1008:


Github user jjmeyer0 closed the pull request at:

https://github.com/apache/metron/pull/632


> Migrate Travis build to use Trusty
> --
>
> Key: METRON-1008
> URL: https://issues.apache.org/jira/browse/METRON-1008
> Project: Metron
>  Issue Type: Bug
>Reporter: Justin Leet
>
> [~zeo...@gmail.com] pinged someone from Travis while we were working on 
> METRON-1004.  In addition to confirming that we should be using a VM, it was 
> also suggested we move to Trusty.  This was briefly looked at in during 
> METRON-1004, in particular because it (theoretically) has the correct version 
> of compilers installed, so we could avoid the hit of setting that up.  It 
> blew up on `npm install`, possibly from my own ignorance.
> At minimum we should move to Trusty:
> {code}
> https://docs.travis-ci.com/user/trusty-ci-environment/
> {code}
> Ideally, we do some more thorough investigation of the compiler and see if we 
> can cut out that step.
> See:
> https://docs.travis-ci.com/user/trusty-ci-environment/



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (METRON-1008) Migrate Travis build to use Trusty

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075359#comment-16075359
 ] 

ASF GitHub Bot commented on METRON-1008:


Github user justinleet commented on the issue:

https://github.com/apache/metron/pull/632
  
@JonZeolla ahh, I thought you were just making a note, so everyone knew 
that recommendation.  Sorry about that.


> Migrate Travis build to use Trusty
> --
>
> Key: METRON-1008
> URL: https://issues.apache.org/jira/browse/METRON-1008
> Project: Metron
>  Issue Type: Bug
>Reporter: Justin Leet
>
> [~zeo...@gmail.com] pinged someone from Travis while we were working on 
> METRON-1004.  In addition to confirming that we should be using a VM, it was 
> also suggested we move to Trusty.  This was briefly looked at in during 
> METRON-1004, in particular because it (theoretically) has the correct version 
> of compilers installed, so we could avoid the hit of setting that up.  It 
> blew up on `npm install`, possibly from my own ignorance.
> At minimum we should move to Trusty:
> {code}
> https://docs.travis-ci.com/user/trusty-ci-environment/
> {code}
> Ideally, we do some more thorough investigation of the compiler and see if we 
> can cut out that step.
> See:
> https://docs.travis-ci.com/user/trusty-ci-environment/



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (METRON-1008) Migrate Travis build to use Trusty

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075352#comment-16075352
 ] 

ASF GitHub Bot commented on METRON-1008:


Github user jjmeyer0 commented on the issue:

https://github.com/apache/metron/pull/632
  
@JonZeolla that was a squashed commit that was probably a typo. I'll remove 
it.


> Migrate Travis build to use Trusty
> --
>
> Key: METRON-1008
> URL: https://issues.apache.org/jira/browse/METRON-1008
> Project: Metron
>  Issue Type: Bug
>Reporter: Justin Leet
>
> [~zeo...@gmail.com] pinged someone from Travis while we were working on 
> METRON-1004.  In addition to confirming that we should be using a VM, it was 
> also suggested we move to Trusty.  This was briefly looked at in during 
> METRON-1004, in particular because it (theoretically) has the correct version 
> of compilers installed, so we could avoid the hit of setting that up.  It 
> blew up on `npm install`, possibly from my own ignorance.
> At minimum we should move to Trusty:
> {code}
> https://docs.travis-ci.com/user/trusty-ci-environment/
> {code}
> Ideally, we do some more thorough investigation of the compiler and see if we 
> can cut out that step.
> See:
> https://docs.travis-ci.com/user/trusty-ci-environment/



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (METRON-1008) Migrate Travis build to use Trusty

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075353#comment-16075353
 ] 

ASF GitHub Bot commented on METRON-1008:


Github user ottobackwards commented on the issue:

https://github.com/apache/metron/pull/632
  
I'm going to be honest.  Now that we have the builds kind of working again, 
I'm a little hesitant to change them for anything but an absolute certainty of 
a return, that we completely understand.

I think the travis build strategy should be a longer living branch maybe.


> Migrate Travis build to use Trusty
> --
>
> Key: METRON-1008
> URL: https://issues.apache.org/jira/browse/METRON-1008
> Project: Metron
>  Issue Type: Bug
>Reporter: Justin Leet
>
> [~zeo...@gmail.com] pinged someone from Travis while we were working on 
> METRON-1004.  In addition to confirming that we should be using a VM, it was 
> also suggested we move to Trusty.  This was briefly looked at in during 
> METRON-1004, in particular because it (theoretically) has the correct version 
> of compilers installed, so we could avoid the hit of setting that up.  It 
> blew up on `npm install`, possibly from my own ignorance.
> At minimum we should move to Trusty:
> {code}
> https://docs.travis-ci.com/user/trusty-ci-environment/
> {code}
> Ideally, we do some more thorough investigation of the compiler and see if we 
> can cut out that step.
> See:
> https://docs.travis-ci.com/user/trusty-ci-environment/



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (METRON-1008) Migrate Travis build to use Trusty

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075346#comment-16075346
 ] 

ASF GitHub Bot commented on METRON-1008:


Github user JonZeolla commented on the issue:

https://github.com/apache/metron/pull/632
  
I was addressing "Testing sudo as false." In the body of the message above.


> Migrate Travis build to use Trusty
> --
>
> Key: METRON-1008
> URL: https://issues.apache.org/jira/browse/METRON-1008
> Project: Metron
>  Issue Type: Bug
>Reporter: Justin Leet
>
> [~zeo...@gmail.com] pinged someone from Travis while we were working on 
> METRON-1004.  In addition to confirming that we should be using a VM, it was 
> also suggested we move to Trusty.  This was briefly looked at in during 
> METRON-1004, in particular because it (theoretically) has the correct version 
> of compilers installed, so we could avoid the hit of setting that up.  It 
> blew up on `npm install`, possibly from my own ignorance.
> At minimum we should move to Trusty:
> {code}
> https://docs.travis-ci.com/user/trusty-ci-environment/
> {code}
> Ideally, we do some more thorough investigation of the compiler and see if we 
> can cut out that step.
> See:
> https://docs.travis-ci.com/user/trusty-ci-environment/



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (METRON-1008) Migrate Travis build to use Trusty

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075337#comment-16075337
 ] 

ASF GitHub Bot commented on METRON-1008:


Github user justinleet commented on the issue:

https://github.com/apache/metron/pull/632
  
I'd be inclined towards avoiding splitting the build if we were only 
getting a couple minutes out of it.  I'm a little worried about being able to 
get three slots on the occasionally stretched Apache setup.  Integration tests 
and building are the long poles in the tent, so splitting out the other tests 
doesn't really save us much time here, unfortunately.


> Migrate Travis build to use Trusty
> --
>
> Key: METRON-1008
> URL: https://issues.apache.org/jira/browse/METRON-1008
> Project: Metron
>  Issue Type: Bug
>Reporter: Justin Leet
>
> [~zeo...@gmail.com] pinged someone from Travis while we were working on 
> METRON-1004.  In addition to confirming that we should be using a VM, it was 
> also suggested we move to Trusty.  This was briefly looked at in during 
> METRON-1004, in particular because it (theoretically) has the correct version 
> of compilers installed, so we could avoid the hit of setting that up.  It 
> blew up on `npm install`, possibly from my own ignorance.
> At minimum we should move to Trusty:
> {code}
> https://docs.travis-ci.com/user/trusty-ci-environment/
> {code}
> Ideally, we do some more thorough investigation of the compiler and see if we 
> can cut out that step.
> See:
> https://docs.travis-ci.com/user/trusty-ci-environment/



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (METRON-1008) Migrate Travis build to use Trusty

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075328#comment-16075328
 ] 

ASF GitHub Bot commented on METRON-1008:


Github user justinleet commented on the issue:

https://github.com/apache/metron/pull/632
  
@JonZeolla Completely counterintuitively, `sudo: required` is the 
counterpart of `sudo: false`.  So this already got taken care of as part of 
METRON-1004.  See: https://docs.travis-ci.com/user/trusty-ci-environment.

If you check out the Travis build 
(https://travis-ci.org/apache/metron/jobs/250503026, for example), it says it's 
running the Trusty as expected.


> Migrate Travis build to use Trusty
> --
>
> Key: METRON-1008
> URL: https://issues.apache.org/jira/browse/METRON-1008
> Project: Metron
>  Issue Type: Bug
>Reporter: Justin Leet
>
> [~zeo...@gmail.com] pinged someone from Travis while we were working on 
> METRON-1004.  In addition to confirming that we should be using a VM, it was 
> also suggested we move to Trusty.  This was briefly looked at in during 
> METRON-1004, in particular because it (theoretically) has the correct version 
> of compilers installed, so we could avoid the hit of setting that up.  It 
> blew up on `npm install`, possibly from my own ignorance.
> At minimum we should move to Trusty:
> {code}
> https://docs.travis-ci.com/user/trusty-ci-environment/
> {code}
> Ideally, we do some more thorough investigation of the compiler and see if we 
> can cut out that step.
> See:
> https://docs.travis-ci.com/user/trusty-ci-environment/



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (METRON-1008) Migrate Travis build to use Trusty

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075322#comment-16075322
 ] 

ASF GitHub Bot commented on METRON-1008:


GitHub user jjmeyer0 reopened a pull request:

https://github.com/apache/metron/pull/632

METRON-1008: Updating travis to use trusty

….npm to cache.

Added some more cacheing from 1004 ticket.

Revert some changes.

Reverted environment and put maven opts in the correct spot.

Testing sudo as false.

Trying multiple vm build.

Revert back to two threads on maven install.

## Contributor Comments
I made travis use trusty. On top of this the following were added before 
1004 was made, but I thought some things were worth keeping:

* Call to verify license is made right away to get quicker failures. 
* Cache $HOME/.npm; After bringing in METRON-1004 it looks like this may 
not be needed anymore?
* Set MAVEN_OPTS to set `-Xmx2g` out of curiosity
* Out of curiosity, multiple environments were added to see if build times 
would dramatically increase. I know this may be undesirable, but I thought I'd 
leave it in to discuss some. I'm leaning towards reverting this back as it only 
seems to get it down to ~23 minutes. Any thoughts?


## Pull Request Checklist

Thank you for submitting a contribution to Apache Metron.  
Please refer to our [Development 
Guidelines](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61332235)
 for the complete guide to follow for contributions.  
Please refer also to our [Build Verification 
Guidelines](https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds?show-miniview)
 for complete smoke testing guides.  


In order to streamline the review of the contribution we ask you follow 
these guidelines and ask you to double check the following:

### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? If not one needs to 
be created at [Metron 
Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel).
 
- [ ] Does your PR title start with METRON- where  is the JIRA 
number you are trying to resolve? Pay particular attention to the hyphen "-" 
character.
- [ ] Has your PR been rebased against the latest commit within the target 
branch (typically master)?


### For code changes:
- [ ] Have you included steps to reproduce the behavior or problem that is 
being changed or addressed?
- [ ] Have you included steps or a guide to how the change may be verified 
and tested manually?
- [ ] Have you ensured that the full suite of tests and checks have been 
executed in the root incubating-metron folder via:
  ```
  mvn -q clean integration-test install && build_utils/verify_licenses.sh 
  ```

- [ ] Have you written or updated unit tests and or integration tests to 
verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [ ] Have you verified the basic functionality of the build by building 
and running locally with Vagrant full-dev environment or the equivalent?

### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in 
which it is rendered by building and verifying the site-book? If not then run 
the following commands and the verify changes via 
`site-book/target/site/index.html`:

  ```
  cd site-book
  mvn site
  ```

 Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.
It is also recommended that [travis-ci](https://travis-ci.org) is set up 
for your personal repository such that your branches are built there before 
submitting a pull request.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jjmeyer0/incubator-metron METRON-1008

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/metron/pull/632.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #632


commit cc9f234fd51493684767c854fc52d0fba7856496
Author: JJ 
Date:   2017-06-29T22:43:58Z

METRON-1008: Updating travis to use trusty, increase heap, and added .npm 
to cache.

Added some more cacheing from 1004 ticket.

Revert some changes.

Reverted environment and put maven opts in the correct spot.

Testing sudo as false.

Trying multiple vm build.

Revert 

[jira] [Commented] (METRON-1008) Migrate Travis build to use Trusty

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075288#comment-16075288
 ] 

ASF GitHub Bot commented on METRON-1008:


Github user jjmeyer0 closed the pull request at:

https://github.com/apache/metron/pull/632


> Migrate Travis build to use Trusty
> --
>
> Key: METRON-1008
> URL: https://issues.apache.org/jira/browse/METRON-1008
> Project: Metron
>  Issue Type: Bug
>Reporter: Justin Leet
>
> [~zeo...@gmail.com] pinged someone from Travis while we were working on 
> METRON-1004.  In addition to confirming that we should be using a VM, it was 
> also suggested we move to Trusty.  This was briefly looked at in during 
> METRON-1004, in particular because it (theoretically) has the correct version 
> of compilers installed, so we could avoid the hit of setting that up.  It 
> blew up on `npm install`, possibly from my own ignorance.
> At minimum we should move to Trusty:
> {code}
> https://docs.travis-ci.com/user/trusty-ci-environment/
> {code}
> Ideally, we do some more thorough investigation of the compiler and see if we 
> can cut out that step.
> See:
> https://docs.travis-ci.com/user/trusty-ci-environment/



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (METRON-1008) Migrate Travis build to use Trusty

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075280#comment-16075280
 ] 

ASF GitHub Bot commented on METRON-1008:


GitHub user jjmeyer0 opened a pull request:

https://github.com/apache/metron/pull/632

METRON-1008: Updating travis to use trusty

….npm to cache.

Added some more cacheing from 1004 ticket.

Revert some changes.

Reverted environment and put maven opts in the correct spot.

Testing sudo as false.

Trying multiple vm build.

Revert back to two threads on maven install.

## Contributor Comments
I made travis use trusty. On top of this the following were added before 
1004 was made, but I thought some things were worth keeping:

* Call to verify license is made right away to get quicker failures. 
* Cache $HOME/.npm; After bringing in METRON-1004 it looks like this may 
not be needed anymore?
* Set MAVEN_OPTS to set `-Xmx2g` out of curiosity
* Out of curiosity, multiple environments were added to see if build times 
would dramatically increase. I know this may be undesirable, but I thought I'd 
leave it in to discuss some. I'm leaning towards reverting this back as it only 
seems to get it down to ~23 minutes. Any thoughts?


## Pull Request Checklist

Thank you for submitting a contribution to Apache Metron.  
Please refer to our [Development 
Guidelines](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61332235)
 for the complete guide to follow for contributions.  
Please refer also to our [Build Verification 
Guidelines](https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds?show-miniview)
 for complete smoke testing guides.  


In order to streamline the review of the contribution we ask you follow 
these guidelines and ask you to double check the following:

### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? If not one needs to 
be created at [Metron 
Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel).
 
- [ ] Does your PR title start with METRON- where  is the JIRA 
number you are trying to resolve? Pay particular attention to the hyphen "-" 
character.
- [ ] Has your PR been rebased against the latest commit within the target 
branch (typically master)?


### For code changes:
- [ ] Have you included steps to reproduce the behavior or problem that is 
being changed or addressed?
- [ ] Have you included steps or a guide to how the change may be verified 
and tested manually?
- [ ] Have you ensured that the full suite of tests and checks have been 
executed in the root incubating-metron folder via:
  ```
  mvn -q clean integration-test install && build_utils/verify_licenses.sh 
  ```

- [ ] Have you written or updated unit tests and or integration tests to 
verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [ ] Have you verified the basic functionality of the build by building 
and running locally with Vagrant full-dev environment or the equivalent?

### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in 
which it is rendered by building and verifying the site-book? If not then run 
the following commands and the verify changes via 
`site-book/target/site/index.html`:

  ```
  cd site-book
  mvn site
  ```

 Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.
It is also recommended that [travis-ci](https://travis-ci.org) is set up 
for your personal repository such that your branches are built there before 
submitting a pull request.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jjmeyer0/incubator-metron METRON-1008

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/metron/pull/632.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #632


commit cc9f234fd51493684767c854fc52d0fba7856496
Author: JJ 
Date:   2017-06-29T22:43:58Z

METRON-1008: Updating travis to use trusty, increase heap, and added .npm 
to cache.

Added some more cacheing from 1004 ticket.

Revert some changes.

Reverted environment and put maven opts in the correct spot.

Testing sudo as false.

Trying multiple vm build.

Revert 

[jira] [Assigned] (METRON-1012) Update Metron public web site for 0.4.0 release

[Matt Foley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/METRON-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Foley reassigned METRON-1012:
--

Assignee: Matt Foley

> Update Metron public web site for 0.4.0 release
> ---
>
> Key: METRON-1012
> URL: https://issues.apache.org/jira/browse/METRON-1012
> Project: Metron
>  Issue Type: Task
>Reporter: Matt Foley
>Assignee: Matt Foley
>
> The public web site source is at 
> https://github.com/apache/metron/tree/master/site
> Update it for the 0.4.0 release.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (METRON-1012) Update Metron public web site for 0.4.0 release

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075140#comment-16075140
 ] 

ASF GitHub Bot commented on METRON-1012:


Github user asfgit closed the pull request at:

https://github.com/apache/metron/pull/629


> Update Metron public web site for 0.4.0 release
> ---
>
> Key: METRON-1012
> URL: https://issues.apache.org/jira/browse/METRON-1012
> Project: Metron
>  Issue Type: Task
>Reporter: Matt Foley
>
> The public web site source is at 
> https://github.com/apache/metron/tree/master/site
> Update it for the 0.4.0 release.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (METRON-1012) Update Metron public web site for 0.4.0 release

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075118#comment-16075118
 ] 

ASF GitHub Bot commented on METRON-1012:


Github user mattf-horton commented on the issue:

https://github.com/apache/metron/pull/629
  
Thanks, I'll proceed on @justinleet and @ottobackwards 's +1s.


> Update Metron public web site for 0.4.0 release
> ---
>
> Key: METRON-1012
> URL: https://issues.apache.org/jira/browse/METRON-1012
> Project: Metron
>  Issue Type: Task
>Reporter: Matt Foley
>
> The public web site source is at 
> https://github.com/apache/metron/tree/master/site
> Update it for the 0.4.0 release.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (METRON-1012) Update Metron public web site for 0.4.0 release

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075095#comment-16075095
 ] 

ASF GitHub Bot commented on METRON-1012:


Github user JonZeolla commented on the issue:

https://github.com/apache/metron/pull/629
  
I didn't review it, but I have no reason to hold it back.


> Update Metron public web site for 0.4.0 release
> ---
>
> Key: METRON-1012
> URL: https://issues.apache.org/jira/browse/METRON-1012
> Project: Metron
>  Issue Type: Task
>Reporter: Matt Foley
>
> The public web site source is at 
> https://github.com/apache/metron/tree/master/site
> Update it for the 0.4.0 release.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (METRON-1019) Metron 0.4.0 manual installation guide for CentOS 6

[Otto Fowler (JIRA)]

Otto Fowler created METRON-1019:
---

 Summary: Metron 0.4.0 manual installation guide for CentOS 6 
 Key: METRON-1019
 URL: https://issues.apache.org/jira/browse/METRON-1019
 Project: Metron
  Issue Type: Improvement
Reporter: Otto Fowler
Assignee: Otto Fowler


This guide will how to install Metron 0.4.0 with HDP 
2.5 bare-metal install on Centos 6 with MySQL for Metron REST and Apache 
NiFi for log ingestion. Basically, it's a manual install of the full dev 
environment with some additions.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (METRON-809) Error while running metron_full_install.yml

[Jon Zeolla (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075076#comment-16075076
 ] 

Jon Zeolla commented on METRON-809:
---

Can you please give this another try with 0.4.0?  

> Error while running metron_full_install.yml
> ---
>
> Key: METRON-809
> URL: https://issues.apache.org/jira/browse/METRON-809
> Project: Metron
>  Issue Type: Bug
> Environment: Centos 6
>Reporter: shriram
>Priority: Blocker
> Attachments: Capture.JPG
>
>
> I am trying to install Metron cluster in AWS with CentOS 6. I encountered the 
> following error while running metron_full_install.yml, at its last step:
> "[ERROR] Failed to execute goal 
> org.codehaus.mojo:exec-maven-plugin:1.5.0:exec (docker-build) on project 
> metron-rpm: Command execution failed. Cannot run program \"docker\" (in 
> directory 
> \"/opt/incubator-metron/metron-deployment/packaging/docker/rpm-docker\"): 
> error=2, No such file or directory -> [Help 1]", "[ERROR] ", "[ERROR] To see 
> the full stack trace of the errors, re-run Maven with the -e switch.", 
> "[ERROR] Re-run Maven using the -X switch to enable full debug logging.", 
> "[ERROR] ", "[ERROR] For more information about the errors and possible 
> solutions, please read the following articles:", "[ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException;, 
> "[ERROR] ", "[ERROR] After correcting the problems, you can resume the build 
> with the command", "[ERROR]   mvn  -rf :metron-rpm"], "warnings": []}
> Attaching screenshot for more details.
> Thanks.
> Regards,
> Shriram



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (METRON-1012) Update Metron public web site for 0.4.0 release

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075075#comment-16075075
 ] 

ASF GitHub Bot commented on METRON-1012:


Github user mattf-horton commented on the issue:

https://github.com/apache/metron/pull/629
  
Hi @JonZeolla , you're quite right, I forgot I already opened METRON-718.
Are we okay to push this patch then?


> Update Metron public web site for 0.4.0 release
> ---
>
> Key: METRON-1012
> URL: https://issues.apache.org/jira/browse/METRON-1012
> Project: Metron
>  Issue Type: Task
>Reporter: Matt Foley
>
> The public web site source is at 
> https://github.com/apache/metron/tree/master/site
> Update it for the 0.4.0 release.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (METRON-939) Upgrade ElasticSearch and Kibana

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075074#comment-16075074
 ] 

ASF GitHub Bot commented on METRON-939:
---

Github user wardbekker commented on the issue:

https://github.com/apache/metron/pull/619
  
@JonZeolla done. 


> Upgrade ElasticSearch and Kibana
> 
>
> Key: METRON-939
> URL: https://issues.apache.org/jira/browse/METRON-939
> Project: Metron
>  Issue Type: Improvement
>Reporter: Jon Zeolla
>
> Upgrade ElasticSearch and Kibana (latest is 5.4 as of writing this).  Among 
> other benefits, this allows us to use periods in field names 
> (https://github.com/elastic/elasticsearch/pull/19937/files), which has been 
> available as of 5.0 and 2.4, and the ability to index an IPv6 address 
> properly 
> (https://www.elastic.co/blog/indexing-ipv6-addresses-in-elasticsearch).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (METRON-1018) Integration tests should reference flux yaml and property files deployed by Ambari

[Ryan Merriman (JIRA)]

Ryan Merriman created METRON-1018:
-

 Summary: Integration tests should reference flux yaml and property 
files deployed by Ambari
 Key: METRON-1018
 URL: https://issues.apache.org/jira/browse/METRON-1018
 Project: Metron
  Issue Type: Bug
Reporter: Ryan Merriman
Assignee: Ryan Merriman


This is a follow-up to METRON-990.  During the review of that Jira it was 
discovered that our integration tests are not referencing the actual flux yaml 
and property files that are used in a Metron installation.  This means the 
integration tests must also be maintained separately with no automated 
protection against regression in cases where flux yaml or property files change.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (METRON-1014) StellarShell class name typo

[Matt Foley (JIRA)]

 [ 
https://issues.apache.org/jira/browse/METRON-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Foley reassigned METRON-1014:
--

Assignee: Matt Foley

> StellarShell class name typo
> 
>
> Key: METRON-1014
> URL: https://issues.apache.org/jira/browse/METRON-1014
> Project: Metron
>  Issue Type: Bug
>Reporter: Matt Foley
>Assignee: Matt Foley
>
> [~ottobackwards] correctly observed: The stellar script 
> https://github.com/apache/metron/blob/master/metron-platform/metron-common/src/main/scripts/stellar
> is using the wrong main class  ( stellar.stellar.shell instead of 
> stellar.common.shell ).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (METRON-939) Upgrade ElasticSearch and Kibana

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075029#comment-16075029
 ] 

ASF GitHub Bot commented on METRON-939:
---

Github user JonZeolla commented on the issue:

https://github.com/apache/metron/pull/619
  
@wardbekker Can you please merge master and deconflict?


> Upgrade ElasticSearch and Kibana
> 
>
> Key: METRON-939
> URL: https://issues.apache.org/jira/browse/METRON-939
> Project: Metron
>  Issue Type: Improvement
>Reporter: Jon Zeolla
>
> Upgrade ElasticSearch and Kibana (latest is 5.4 as of writing this).  Among 
> other benefits, this allows us to use periods in field names 
> (https://github.com/elastic/elasticsearch/pull/19937/files), which has been 
> available as of 5.0 and 2.4, and the ability to index an IPv6 address 
> properly 
> (https://www.elastic.co/blog/indexing-ipv6-addresses-in-elasticsearch).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (METRON-1017) Ambari components should be separate

[Ryan Merriman (JIRA)]

Ryan Merriman created METRON-1017:
-

 Summary: Ambari components should be separate
 Key: METRON-1017
 URL: https://issues.apache.org/jira/browse/METRON-1017
 Project: Metron
  Issue Type: Bug
Reporter: Ryan Merriman
Assignee: Ryan Merriman


This is a follow-up to METRON-990.  During the review of that Jira it was 
pointed out that a config change should only prompt a restart of the affected 
component(s), not all components every time like it does now.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (METRON-990) Clean up and organize flux properties

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075009#comment-16075009
 ] 

ASF GitHub Bot commented on METRON-990:
---

Github user asfgit closed the pull request at:

https://github.com/apache/metron/pull/613


> Clean up and organize flux properties
> -
>
> Key: METRON-990
> URL: https://issues.apache.org/jira/browse/METRON-990
> Project: Metron
>  Issue Type: Improvement
>Reporter: Ryan Merriman
>Assignee: Ryan Merriman
>
> There are several flux properties that are not being used anymore.  There are 
> also several hardcoded values in flux files that should be configurable.  A 
> review of the flux files is needed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (METRON-1016) METRON Demo System as separate install option

[Otto Fowler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/METRON-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Otto Fowler reassigned METRON-1016:
---

Assignee: Otto Fowler

> METRON Demo System as separate install option
> -
>
> Key: METRON-1016
> URL: https://issues.apache.org/jira/browse/METRON-1016
> Project: Metron
>  Issue Type: Bug
>Reporter: Otto Fowler
>Assignee: Otto Fowler
>
> Right now, the demo system ( bro, snort, yaf ) are part of the default 
> installation, and the default configurations required for those systems ( ES, 
> Enrichment ) are in the main code base.  For example bro's default enrichment 
> is the enrichment that assumes the demo setup.
> This is not really correct.  The demo system should be a separately 
> installable feature of metron, and it's configurations should be managed 
> outside the defaults for the parsers etc.
> This would allow separate development of the demo without affecting others.
> Either checkbox or a separate ambari service?
> What should the default enrichment be?
> How to have vagrant install the service



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (METRON-1016) METRON Demo System as separate install option

[Otto Fowler (JIRA)]

Otto Fowler created METRON-1016:
---

 Summary: METRON Demo System as separate install option
 Key: METRON-1016
 URL: https://issues.apache.org/jira/browse/METRON-1016
 Project: Metron
  Issue Type: Bug
Reporter: Otto Fowler


Right now, the demo system ( bro, snort, yaf ) are part of the default 
installation, and the default configurations required for those systems ( ES, 
Enrichment ) are in the main code base.  For example bro's default enrichment 
is the enrichment that assumes the demo setup.

This is not really correct.  The demo system should be a separately installable 
feature of metron, and it's configurations should be managed outside the 
defaults for the parsers etc.

This would allow separate development of the demo without affecting others.

Either checkbox or a separate ambari service?
What should the default enrichment be?
How to have vagrant install the service





--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (METRON-633) Create better logging for HbaseEnrichmentWriter

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074793#comment-16074793
 ] 

ASF GitHub Bot commented on METRON-633:
---

Github user justinleet commented on the issue:

https://github.com/apache/metron/pull/572
  
@zezutom When you have a chance, could you merge in master and deconflict 
this?  The Travis build timeouts should be fixed as of 
https://github.com/apache/metron/pull/624.  Sorry about the trouble with 
Travis, and I look forward to getting this into master.


> Create better logging for HbaseEnrichmentWriter
> ---
>
> Key: METRON-633
> URL: https://issues.apache.org/jira/browse/METRON-633
> Project: Metron
>  Issue Type: Bug
>Reporter: Casey Stella
>Assignee: Tomas Zezula
>  Labels: newbie
>
> Right now our debug logging is nonexistent for this writer and it makes 
> tracking down issues almost impossible.  This should be corrected. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (METRON-746) Build Custom Checkstyle and IDE formatting settings

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074735#comment-16074735
 ] 

ASF GitHub Bot commented on METRON-746:
---

Github user justinleet commented on the issue:

https://github.com/apache/metron/pull/577
  
@mmiklavc I still haven't found (significant) issues with autoformat + 
checkstyle, assuming both the checkstyle is setup and the autoformatting is 
setup (preferably with Google's IntelliJ settings).  Are you okay with merging 
this in, and filing follow-on tickets for any issues?  Or is there something in 
particular you'd like to see done here?


> Build Custom Checkstyle and IDE formatting settings
> ---
>
> Key: METRON-746
> URL: https://issues.apache.org/jira/browse/METRON-746
> Project: Metron
>  Issue Type: Improvement
>Reporter: Justin Leet
>Assignee: Justin Leet
>Priority: Minor
>
> We need a custom checkstyle.xml based off the sun convention checkstyle.  
> Based on a discussion thread, there are a few things that need to be setup
> * Two space indents
> * Line Length longer than 80 (pretty popular in the discussion, but not 
> officially part of our code style)
> * Appropriate warn/error levels set so we don't immediately start failing 
> every build.
> * Importable IntelliJ code style at minimum, but I'd also like to see Eclipse 
> if possible to avoid forcing a given dev environment.  IntelliJ allows for 
> importing a checkstyle.xml to use as the basis.  We can export the resulting 
> formatting settings for people.
> * Ensure Travis actually runs checkstyle during our builds



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (METRON-1012) Update Metron public web site for 0.4.0 release

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074706#comment-16074706
 ] 

ASF GitHub Bot commented on METRON-1012:


Github user ottobackwards commented on the issue:

https://github.com/apache/metron/pull/629
  
+1


> Update Metron public web site for 0.4.0 release
> ---
>
> Key: METRON-1012
> URL: https://issues.apache.org/jira/browse/METRON-1012
> Project: Metron
>  Issue Type: Task
>Reporter: Matt Foley
>
> The public web site source is at 
> https://github.com/apache/metron/tree/master/site
> Update it for the 0.4.0 release.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (METRON-1014) StellarShell class name typo

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074689#comment-16074689
 ] 

ASF GitHub Bot commented on METRON-1014:


Github user ottobackwards commented on the issue:

https://github.com/apache/metron/pull/630
  
+1 - I have been preforming this same operation in my vm's manually, this 
is the fix


> StellarShell class name typo
> 
>
> Key: METRON-1014
> URL: https://issues.apache.org/jira/browse/METRON-1014
> Project: Metron
>  Issue Type: Bug
>Reporter: Matt Foley
>
> [~ottobackwards] correctly observed: The stellar script 
> https://github.com/apache/metron/blob/master/metron-platform/metron-common/src/main/scripts/stellar
> is using the wrong main class  ( stellar.stellar.shell instead of 
> stellar.common.shell ).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (METRON-1012) Update Metron public web site for 0.4.0 release

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074658#comment-16074658
 ] 

ASF GitHub Bot commented on METRON-1012:


Github user JonZeolla commented on the issue:

https://github.com/apache/metron/pull/629
  
@mattf-horton Okay great, sounds good to me.  I did a quick search before 
opening a new JIRA and it looks like you've already addressed this in 
[METRON-718](https://issues.apache.org/jira/browse/METRON-718).


> Update Metron public web site for 0.4.0 release
> ---
>
> Key: METRON-1012
> URL: https://issues.apache.org/jira/browse/METRON-1012
> Project: Metron
>  Issue Type: Task
>Reporter: Matt Foley
>
> The public web site source is at 
> https://github.com/apache/metron/tree/master/site
> Update it for the 0.4.0 release.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (METRON-508) Expand Elasticsearch templates to support the standard bro logs

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074620#comment-16074620
 ] 

ASF GitHub Bot commented on METRON-508:
---

Github user asfgit closed the pull request at:

https://github.com/apache/metron/pull/586


> Expand Elasticsearch templates to support the standard bro logs
> ---
>
> Key: METRON-508
> URL: https://issues.apache.org/jira/browse/METRON-508
> Project: Metron
>  Issue Type: Sub-task
>Reporter: Jon Zeolla
>Assignee: Jon Zeolla
>Priority: Minor
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> The current elasticsearch templates do not support any logs other than Conn, 
> HTTP, and DNS.  We should provide additional templates so that an 
> out-of-the-box bro install can send all of its logs into Metron and they will 
> get probably indexed in elasticsearch.  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (METRON-1012) Update Metron public web site for 0.4.0 release

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074507#comment-16074507
 ] 

ASF GitHub Bot commented on METRON-1012:


Github user justinleet commented on the issue:

https://github.com/apache/metron/pull/629
  
@mattf-horton To the best of my knowledge, this was the last pass that gets 
rid of the remaining incubator terminology.  Only things left are old news 
items and so on that are actually from or about incubation. Thanks for taking 
care of the wiki, too.  I hadn't looked at it enough for incubating stuff.


> Update Metron public web site for 0.4.0 release
> ---
>
> Key: METRON-1012
> URL: https://issues.apache.org/jira/browse/METRON-1012
> Project: Metron
>  Issue Type: Task
>Reporter: Matt Foley
>
> The public web site source is at 
> https://github.com/apache/metron/tree/master/site
> Update it for the 0.4.0 release.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (METRON-1014) StellarShell class name typo

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074466#comment-16074466
 ] 

ASF GitHub Bot commented on METRON-1014:


GitHub user mattf-horton opened a pull request:

https://github.com/apache/metron/pull/630

METRON-1014 StellarShell class name typo

## Contributor Comments
Fix a path typo

To test is trivial, but unfortunately requires building and then launching 
quick-dev or other install, then invoke the stellar shell script.  If it 
launches successfully the bug is fixed.  It currently errors on a Class Not 
Found error.

I've opened METRON-1015 to create an integration test for this issue 
(problem in the CLI independent of the Stellar executor).

## Pull Request Checklist

### For all changes:
- [x] Is there a JIRA ticket associated with this PR? If not one needs to 
be created at [Metron 
Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel).
 
- [x] Does your PR title start with METRON- where  is the JIRA 
number you are trying to resolve? Pay particular attention to the hyphen "-" 
character.
- [x] Has your PR been rebased against the latest commit within the target 
branch (typically master)?


### For code changes:
- [x] Have you included steps to reproduce the behavior or problem that is 
being changed or addressed?
- [x] Have you included steps or a guide to how the change may be verified 
and tested manually?
- [NA] Have you ensured that the full suite of tests and checks have been 
executed in the root incubating-metron folder via:
  ```
  mvn -q clean integration-test install && build_utils/verify_licenses.sh 
  ```

- [NA] Have you written or updated unit tests and or integration tests to 
verify your changes?
- [NA] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [x] Have you verified the basic functionality of the build by building 
and running locally with Vagrant full-dev environment or the equivalent?

### For documentation related changes: NA

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/mattf-horton/metron METRON-1014

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/metron/pull/630.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #630


commit a95c8ad69185e6265f81add6bf151229bf48fec5
Author: mattf-horton 
Date:   2017-07-05T09:09:52Z

METRON-1014 StellarShell class name typo




> StellarShell class name typo
> 
>
> Key: METRON-1014
> URL: https://issues.apache.org/jira/browse/METRON-1014
> Project: Metron
>  Issue Type: Bug
>Reporter: Matt Foley
>
> [~ottobackwards] correctly observed: The stellar script 
> https://github.com/apache/metron/blob/master/metron-platform/metron-common/src/main/scripts/stellar
> is using the wrong main class  ( stellar.stellar.shell instead of 
> stellar.common.shell ).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (METRON-1015) Write an integration test for the StellarShell CLI

[Matt Foley (JIRA)]

Matt Foley created METRON-1015:
--

 Summary: Write an integration test for the StellarShell CLI
 Key: METRON-1015
 URL: https://issues.apache.org/jira/browse/METRON-1015
 Project: Metron
  Issue Type: Improvement
Reporter: Matt Foley


Write an integration test for the StellarShell CLI, probably using 'expect'.

This would have prevented a recent bug, METRON-1014, in which the shell 
invocation script was broken due to a path error, and other potential bugs in 
the CLI independent of the Stellar executor.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (METRON-1012) Update Metron public web site for 0.4.0 release

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16074325#comment-16074325
 ] 

ASF GitHub Bot commented on METRON-1012:


Github user mattf-horton commented on the issue:

https://github.com/apache/metron/pull/629
  
Hi @justinleet , thanks for looking at this.  I removed instances of 
"incubator" from Website+PR+Merge, and had already fixed other cwiki pages I 
came across.  Any other instances you noticed?

@JonZeolla , once published to dist/release/metron, all older versions 
remain available in http://archive.apache.org/dist/metron/ .  This includes the 
book-site for each version starting with 0.3.1.  So the old docs remain 
available.  (Interestingly, the incubator-metron archives didn't migrate, and 
are still at http://archive.apache.org/dist/incubator/metron/ .  But those 
older versions didn't have site-books included.)

I'd like to see a pull-down list of them (both old books and old releases) 
added to the public web site, but I'm probably not the right person to do that, 
since I have the web design skills of a cow.  Could you please open a new jira 
so we can address that outside of the release mechanics?


> Update Metron public web site for 0.4.0 release
> ---
>
> Key: METRON-1012
> URL: https://issues.apache.org/jira/browse/METRON-1012
> Project: Metron
>  Issue Type: Task
>Reporter: Matt Foley
>
> The public web site source is at 
> https://github.com/apache/metron/tree/master/site
> Update it for the 0.4.0 release.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)