[jira] [Commented] (METRON-1576) bundle.css RAT failure for metron-interface/metron-alerts

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on METRON-1576:


GitHub user justinleet reopened a pull request:

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

METRON-1576: bundle.css RAT failure for metron-interface/metron-alerts

## Contributor Comments
Seen during attempt to cut 0.5.0-RC1.

As previously seen in:
https://issues.apache.org/jira/browse/METRON-1373
https://issues.apache.org/jira/browse/METRON-1163

I went and made it a "*" exclusion.  There was some concern that if we see 
this change, we should potentially be rechecking the license for version 
changes.  In that light, is this change too broad?

To make sure it works, you have to do a bit more work than just building it.
```
git archive --prefix=apache-metron-0.5.0/  | gzip >  
apache-metron-0.5.0.tar.gz
```

untar this file somewhere of your choice.
```
tar xvfz apache-metron-0.5.0.tar.gz
```

go to apache-metron-0.5.0/metron-interface/metron-alerts and run
```
mvn clean install apache-rat:check -DskipTests
```

The build should succeed (and fail without this commit).


## 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:
- [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?
- [ ] Have you ensured that the full suite of tests and checks have been 
executed in the root metron folder via:
  ```
  mvn -q clean integration-test install && 
dev-utilities/build-utils/verify_licenses.sh 
  ```

- [ ] Have you verified the basic functionality of the build by building 
and running locally with Vagrant full-dev environment or the equivalent?

 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/justinleet/metron bundleCssExclusion

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

https://github.com/apache/metron/pull/1029.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 #1029


commit ce11a7db8d9faf6626ed0d409cafa139066de365
Author: justinjleet 
Date:   2018-05-23T22:04:25Z

wildcard the font awesome exclusion




> bundle.css RAT failure for metron-interface/metron-alerts
> -
>
> Key: METRON-1576
> URL: https://issues.apache.org/jira/browse/METRON-1576
> Project: Metron
>  Issue Type: Bug
>Reporter: Justin Leet
>Assignee: Justin Leet
>Priority: Major
>
> Problem seen during creation of 0.5.0 RC
> This occurred a couple other times
> https://issues.apache.org/jira/browse/METRON-1373
> https://issues.apache.org/jira/browse/METRON-1163
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (METRON-1576) bundle.css RAT failure for metron-interface/metron-alerts

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on METRON-1576:


Github user justinleet commented on the issue:

https://github.com/apache/metron/pull/1029
  
kick travis


> bundle.css RAT failure for metron-interface/metron-alerts
> -
>
> Key: METRON-1576
> URL: https://issues.apache.org/jira/browse/METRON-1576
> Project: Metron
>  Issue Type: Bug
>Reporter: Justin Leet
>Assignee: Justin Leet
>Priority: Major
>
> Problem seen during creation of 0.5.0 RC
> This occurred a couple other times
> https://issues.apache.org/jira/browse/METRON-1373
> https://issues.apache.org/jira/browse/METRON-1163
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (METRON-1576) bundle.css RAT failure for metron-interface/metron-alerts

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on METRON-1576:


Github user justinleet closed the pull request at:

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


> bundle.css RAT failure for metron-interface/metron-alerts
> -
>
> Key: METRON-1576
> URL: https://issues.apache.org/jira/browse/METRON-1576
> Project: Metron
>  Issue Type: Bug
>Reporter: Justin Leet
>Assignee: Justin Leet
>Priority: Major
>
> Problem seen during creation of 0.5.0 RC
> This occurred a couple other times
> https://issues.apache.org/jira/browse/METRON-1373
> https://issues.apache.org/jira/browse/METRON-1163
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] metron pull request #1029: METRON-1576: bundle.css RAT failure for metron-in...

[justinleet]

Github user justinleet closed the pull request at:

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


---

[GitHub] metron pull request #1029: METRON-1576: bundle.css RAT failure for metron-in...

[justinleet]

GitHub user justinleet reopened a pull request:

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

METRON-1576: bundle.css RAT failure for metron-interface/metron-alerts

## Contributor Comments
Seen during attempt to cut 0.5.0-RC1.

As previously seen in:
https://issues.apache.org/jira/browse/METRON-1373
https://issues.apache.org/jira/browse/METRON-1163

I went and made it a "*" exclusion.  There was some concern that if we see 
this change, we should potentially be rechecking the license for version 
changes.  In that light, is this change too broad?

To make sure it works, you have to do a bit more work than just building it.
```
git archive --prefix=apache-metron-0.5.0/  | gzip >  
apache-metron-0.5.0.tar.gz
```

untar this file somewhere of your choice.
```
tar xvfz apache-metron-0.5.0.tar.gz
```

go to apache-metron-0.5.0/metron-interface/metron-alerts and run
```
mvn clean install apache-rat:check -DskipTests
```

The build should succeed (and fail without this commit).


## 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:
- [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?
- [ ] Have you ensured that the full suite of tests and checks have been 
executed in the root metron folder via:
  ```
  mvn -q clean integration-test install && 
dev-utilities/build-utils/verify_licenses.sh 
  ```

- [ ] Have you verified the basic functionality of the build by building 
and running locally with Vagrant full-dev environment or the equivalent?

 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/justinleet/metron bundleCssExclusion

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

https://github.com/apache/metron/pull/1029.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 #1029


commit ce11a7db8d9faf6626ed0d409cafa139066de365
Author: justinjleet 
Date:   2018-05-23T22:04:25Z

wildcard the font awesome exclusion




---

[GitHub] metron issue #1029: METRON-1576: bundle.css RAT failure for metron-interface...

[justinleet]

Github user justinleet commented on the issue:

https://github.com/apache/metron/pull/1029
  
kick travis


---

[jira] [Commented] (METRON-1576) bundle.css RAT failure for metron-interface/metron-alerts

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on METRON-1576:


GitHub user justinleet opened a pull request:

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

METRON-1576: bundle.css RAT failure for metron-interface/metron-alerts

## Contributor Comments
Seen during attempt to cut 0.5.0-RC1.

As previously seen in:
https://issues.apache.org/jira/browse/METRON-1373
https://issues.apache.org/jira/browse/METRON-1163

I went and made it a "*" exclusion.  There was some concern that if we see 
this change, we should potentially be rechecking the license for version 
changes.  In that light, is this change too broad?

To make sure it works, you have to do a bit more work than just building it.
```
git archive --prefix=apache-metron-0.5.0/  | gzip >  
apache-metron-0.5.0.tar.gz
```

untar this file somewhere of your choice.
```
tar xvfz apache-metron-0.5.0.tar.gz
```

go to apache-metron-0.5.0/metron-interface/metron-alerts and run
```
mvn clean install apache-rat:check -DskipTests
```

The build should succeed (and fail without this commit).


## 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:
- [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?
- [ ] Have you ensured that the full suite of tests and checks have been 
executed in the root metron folder via:
  ```
  mvn -q clean integration-test install && 
dev-utilities/build-utils/verify_licenses.sh 
  ```

- [ ] Have you verified the basic functionality of the build by building 
and running locally with Vagrant full-dev environment or the equivalent?

 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/justinleet/metron bundleCssExclusion

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

https://github.com/apache/metron/pull/1029.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 #1029


commit ce11a7db8d9faf6626ed0d409cafa139066de365
Author: justinjleet 
Date:   2018-05-23T22:04:25Z

wildcard the font awesome exclusion




> bundle.css RAT failure for metron-interface/metron-alerts
> -
>
> Key: METRON-1576
> URL: https://issues.apache.org/jira/browse/METRON-1576
> Project: Metron
>  Issue Type: Bug
>Reporter: Justin Leet
>Assignee: Justin Leet
>Priority: Major
>
> Problem seen during creation of 0.5.0 RC
> This occurred a couple other times
> https://issues.apache.org/jira/browse/METRON-1373
> https://issues.apache.org/jira/browse/METRON-1163
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] metron pull request #1029: METRON-1576: bundle.css RAT failure for metron-in...

[justinleet]

GitHub user justinleet opened a pull request:

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

METRON-1576: bundle.css RAT failure for metron-interface/metron-alerts

## Contributor Comments
Seen during attempt to cut 0.5.0-RC1.

As previously seen in:
https://issues.apache.org/jira/browse/METRON-1373
https://issues.apache.org/jira/browse/METRON-1163

I went and made it a "*" exclusion.  There was some concern that if we see 
this change, we should potentially be rechecking the license for version 
changes.  In that light, is this change too broad?

To make sure it works, you have to do a bit more work than just building it.
```
git archive --prefix=apache-metron-0.5.0/  | gzip >  
apache-metron-0.5.0.tar.gz
```

untar this file somewhere of your choice.
```
tar xvfz apache-metron-0.5.0.tar.gz
```

go to apache-metron-0.5.0/metron-interface/metron-alerts and run
```
mvn clean install apache-rat:check -DskipTests
```

The build should succeed (and fail without this commit).


## 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:
- [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?
- [ ] Have you ensured that the full suite of tests and checks have been 
executed in the root metron folder via:
  ```
  mvn -q clean integration-test install && 
dev-utilities/build-utils/verify_licenses.sh 
  ```

- [ ] Have you verified the basic functionality of the build by building 
and running locally with Vagrant full-dev environment or the equivalent?

 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/justinleet/metron bundleCssExclusion

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

https://github.com/apache/metron/pull/1029.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 #1029


commit ce11a7db8d9faf6626ed0d409cafa139066de365
Author: justinjleet 
Date:   2018-05-23T22:04:25Z

wildcard the font awesome exclusion




---

[jira] [Created] (METRON-1576) bundle.css RAT failure for metron-interface/metron-alerts

[Justin Leet (JIRA)]

Justin Leet created METRON-1576:
---

 Summary: bundle.css RAT failure for metron-interface/metron-alerts
 Key: METRON-1576
 URL: https://issues.apache.org/jira/browse/METRON-1576
 Project: Metron
  Issue Type: Bug
Reporter: Justin Leet
Assignee: Justin Leet


Problem seen during creation of 0.5.0 RC

This occurred a couple other times

https://issues.apache.org/jira/browse/METRON-1373

https://issues.apache.org/jira/browse/METRON-1163

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (METRON-1566) Alert updates are not propagated to metaalert child alerts

[Justin Leet (JIRA)]

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

Justin Leet reassigned METRON-1566:
---

Assignee: Ryan Merriman

> Alert updates are not propagated to metaalert child alerts
> --
>
> Key: METRON-1566
> URL: https://issues.apache.org/jira/browse/METRON-1566
> Project: Metron
>  Issue Type: Bug
>Reporter: Ryan Merriman
>Assignee: Ryan Merriman
>Priority: Major
> Fix For: 0.5.0
>
>
> This can be reproduced as follows:
>  * Create a metaalert from an alert
>  * Update that alert with the patch endpoint
>  * The change to the alert is not reflected in the metaalert child alert



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (METRON-1566) Alert updates are not propagated to metaalert child alerts

[Justin Leet (JIRA)]

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

Justin Leet updated METRON-1566:

Fix Version/s: 0.5.0

> Alert updates are not propagated to metaalert child alerts
> --
>
> Key: METRON-1566
> URL: https://issues.apache.org/jira/browse/METRON-1566
> Project: Metron
>  Issue Type: Bug
>Reporter: Ryan Merriman
>Assignee: Ryan Merriman
>Priority: Major
> Fix For: 0.5.0
>
>
> This can be reproduced as follows:
>  * Create a metaalert from an alert
>  * Update that alert with the patch endpoint
>  * The change to the alert is not reflected in the metaalert child alert



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (METRON-1575) Add leet gpg public key to the KEYS file

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on METRON-1575:


Github user asfgit closed the pull request at:

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


> Add leet gpg public key to the KEYS file
> 
>
> Key: METRON-1575
> URL: https://issues.apache.org/jira/browse/METRON-1575
> Project: Metron
>  Issue Type: Bug
>Reporter: Justin Leet
>Assignee: Justin Leet
>Priority: Major
> Fix For: 0.5.0
>
>
> Need it to be able to sign releases.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] metron pull request #1028: METRON-1575: Add leet gpg public key to the KEYS ...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[jira] [Updated] (METRON-1575) Add leet gpg public key to the KEYS file

[Justin Leet (JIRA)]

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

Justin Leet updated METRON-1575:

Fix Version/s: 0.5.0

> Add leet gpg public key to the KEYS file
> 
>
> Key: METRON-1575
> URL: https://issues.apache.org/jira/browse/METRON-1575
> Project: Metron
>  Issue Type: Bug
>Reporter: Justin Leet
>Assignee: Justin Leet
>Priority: Major
> Fix For: 0.5.0
>
>
> Need it to be able to sign releases.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (METRON-1575) Add leet gpg public key to the KEYS file

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on METRON-1575:


Github user cestella commented on the issue:

https://github.com/apache/metron/pull/1028
  
+1 by inspection


> Add leet gpg public key to the KEYS file
> 
>
> Key: METRON-1575
> URL: https://issues.apache.org/jira/browse/METRON-1575
> Project: Metron
>  Issue Type: Bug
>Reporter: Justin Leet
>Assignee: Justin Leet
>Priority: Major
>
> Need it to be able to sign releases.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] metron issue #1028: METRON-1575: Add leet gpg public key to the KEYS file

[cestella]

Github user cestella commented on the issue:

https://github.com/apache/metron/pull/1028
  
+1 by inspection


---

[jira] [Commented] (METRON-1575) Add leet gpg public key to the KEYS file

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on METRON-1575:


GitHub user justinleet opened a pull request:

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

METRON-1575: Add leet gpg public key to the KEYS file

## Contributor Comments
Added public key to keyfile.  Make sure nothing seems wrong.

## 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:
- [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:
- [ ] Have you ensured that the full suite of tests and checks have been 
executed in the root metron folder via:
  ```
  mvn -q clean integration-test install && 
dev-utilities/build-utils/verify_licenses.sh 
  ```

 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/justinleet/metron leetKey

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

https://github.com/apache/metron/pull/1028.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 #1028


commit 108a253c027b602c860112693cc19fe308b076c8
Author: justinjleet 
Date:   2018-05-23T18:43:30Z

Adding public key to the file




> Add leet gpg public key to the KEYS file
> 
>
> Key: METRON-1575
> URL: https://issues.apache.org/jira/browse/METRON-1575
> Project: Metron
>  Issue Type: Bug
>Reporter: Justin Leet
>Assignee: Justin Leet
>Priority: Major
>
> Need it to be able to sign releases.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] metron pull request #1028: METRON-1575: Add leet gpg public key to the KEYS ...

[justinleet]

GitHub user justinleet opened a pull request:

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

METRON-1575: Add leet gpg public key to the KEYS file

## Contributor Comments
Added public key to keyfile.  Make sure nothing seems wrong.

## 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:
- [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:
- [ ] Have you ensured that the full suite of tests and checks have been 
executed in the root metron folder via:
  ```
  mvn -q clean integration-test install && 
dev-utilities/build-utils/verify_licenses.sh 
  ```

 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/justinleet/metron leetKey

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

https://github.com/apache/metron/pull/1028.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 #1028


commit 108a253c027b602c860112693cc19fe308b076c8
Author: justinjleet 
Date:   2018-05-23T18:43:30Z

Adding public key to the file




---

[jira] [Created] (METRON-1575) Add leet gpg public key to the KEYS file

[Justin Leet (JIRA)]

Justin Leet created METRON-1575:
---

 Summary: Add leet gpg public key to the KEYS file
 Key: METRON-1575
 URL: https://issues.apache.org/jira/browse/METRON-1575
 Project: Metron
  Issue Type: Bug
Reporter: Justin Leet
Assignee: Justin Leet


Need it to be able to sign releases.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (METRON-1574) Update version to 0.5.0

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on METRON-1574:


Github user asfgit closed the pull request at:

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


> Update version to 0.5.0
> ---
>
> Key: METRON-1574
> URL: https://issues.apache.org/jira/browse/METRON-1574
> Project: Metron
>  Issue Type: Bug
>Reporter: Justin Leet
>Assignee: Justin Leet
>Priority: Major
> Fix For: 0.5.0
>
>
> For the next release, we decided to go with 0.5.0, rather than 0.4.3. This 
> requires bumping the version number per 
> https://cwiki.apache.org/confluence/display/METRON/Release+Process and 
> https://cwiki.apache.org/confluence/display/METRON/Change+the+Build+Version+Number



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] metron pull request #1026: METRON-1574: Update version to 0.5.0

[asfgit]

Github user asfgit closed the pull request at:

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


---

[jira] [Updated] (METRON-1565) Metaalerts fix denormalization after moving to active status

[Nick Allen (JIRA)]

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

Nick Allen updated METRON-1565:
---
Fix Version/s: 0.5.0

> Metaalerts fix denormalization after moving to active status
> 
>
> Key: METRON-1565
> URL: https://issues.apache.org/jira/browse/METRON-1565
> Project: Metron
>  Issue Type: Bug
>Reporter: Ryan Merriman
>Assignee: Ryan Merriman
>Priority: Major
> Fix For: 0.5.0
>
>
> The process of updating from inactive to active is slightly incomplete. Check 
> out 
> [https://github.com/apache/metron/pull/970/files#diff-b7359d01c3ffbed48b7fdaa2d32169e7R246].
> Say we have these three steps:
>  - Metaalert is updated to inactive
>  - (Former) child alert is updated.
>  - Metaalert is made active again.
> The update will be missing from the metaalert. We need to update the 
> metaalert with the current state of any alerts (which we conveniently have 
> because we needed to update them all anyway!). This is a problem with both ES 
> and Solr (which shouldn't be surprising since that link is to the abstract 
> DAO). Basically, this should just be adding all the alerts in the metaalert 
> back into the updated version of the document before passing it to the 
> update. It also needs an associated test case.
> This fix should be made against master and pulled into the Solr branch (and 
> the metaalerts PR afterwards). See 
> [https://github.com/apache/metron/blob/e59059bd9707a6ca46c4137d796b8f2943f06b43/metron-platform/metron-elasticsearch/src/main/java/org/apache/metron/elasticsearch/dao/ElasticsearchMetaAlertDao.java#L351].
>  Main thing might just be reordering the class to build the metaalert update 
> itself after grabbing all the alerts.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (METRON-1574) Update version to 0.5.0

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on METRON-1574:


Github user nickwallen commented on the issue:

https://github.com/apache/metron/pull/1026
  
+1 Looks good @justinleet Thanks!


> Update version to 0.5.0
> ---
>
> Key: METRON-1574
> URL: https://issues.apache.org/jira/browse/METRON-1574
> Project: Metron
>  Issue Type: Bug
>Reporter: Justin Leet
>Assignee: Justin Leet
>Priority: Major
> Fix For: 0.5.0
>
>
> For the next release, we decided to go with 0.5.0, rather than 0.4.3. This 
> requires bumping the version number per 
> https://cwiki.apache.org/confluence/display/METRON/Release+Process and 
> https://cwiki.apache.org/confluence/display/METRON/Change+the+Build+Version+Number



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] metron issue #1026: METRON-1574: Update version to 0.5.0

[nickwallen]

Github user nickwallen commented on the issue:

https://github.com/apache/metron/pull/1026
  
+1 Looks good @justinleet Thanks!


---

[jira] [Commented] (METRON-1421) Create a SolrMetaAlertDao

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on METRON-1421:


Github user justinleet closed the pull request at:

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


> Create a SolrMetaAlertDao
> -
>
> Key: METRON-1421
> URL: https://issues.apache.org/jira/browse/METRON-1421
> Project: Metron
>  Issue Type: Sub-task
>Reporter: Justin Leet
>Assignee: Justin Leet
>Priority: Major
>
> Create an implementation of the MetaAlertDao for Solr. This will involve 
> implementing the various MetaAlertDao methods using the SolrJ library and 
> also providing a SolrMetaAlertIntegrationTest (similar to 
> ElasticsearchMetaAlertIntegrationTest).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (METRON-1421) Create a SolrMetaAlertDao

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on METRON-1421:


Github user justinleet commented on the issue:

https://github.com/apache/metron/pull/970
  
This is merged into the feature branch. Closing PR manually, accordingly.


> Create a SolrMetaAlertDao
> -
>
> Key: METRON-1421
> URL: https://issues.apache.org/jira/browse/METRON-1421
> Project: Metron
>  Issue Type: Sub-task
>Reporter: Justin Leet
>Assignee: Justin Leet
>Priority: Major
>
> Create an implementation of the MetaAlertDao for Solr. This will involve 
> implementing the various MetaAlertDao methods using the SolrJ library and 
> also providing a SolrMetaAlertIntegrationTest (similar to 
> ElasticsearchMetaAlertIntegrationTest).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] metron pull request #970: METRON-1421: Create a SolrMetaAlertDao

[justinleet]

Github user justinleet closed the pull request at:

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


---

[GitHub] metron issue #970: METRON-1421: Create a SolrMetaAlertDao

[justinleet]

Github user justinleet commented on the issue:

https://github.com/apache/metron/pull/970
  
This is merged into the feature branch. Closing PR manually, accordingly.


---

[jira] [Commented] (METRON-1184) EC2 Deployment - Updating control_path to accommodate for Linux

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on METRON-1184:


Github user as22323 commented on the issue:

https://github.com/apache/metron/pull/754
  
Could the following approach be taken?: 

In metron-deployment/amazon-ec2/README.md add two new "Errors" in the 
"Common Error Section"

1) 
# Error: ''Failed to connect to the host via ssh: percent_expand: unknown 
key %C\r\n"

This error might occur if you are deploying with Linux OS. The %C in the 
control_path is compatible with Mac OS but might not be compatible certain 
Linux operating systems.

## Solution
If you see this error update the control_path  in ansble.cfg  to the 
following. 
```
control_path = ~/.ssh/ansbile-ssh-%%h-%%r
```

2) 
# Error: ''too long for Unix domain socket\rn\n"
This error might occur if you are deploying with Mac OS.

## Solution
If you see this error when deploying with a Mac update the control_path in  
ansble.cfg to the following.
```
control_path = ~/.ssh/ansible-ssh-%%C
```

---
Update ansble.cfg to include comments: 
```
#When deploying with Mac OS use this control_path if you receive the 
following error "too long for Unix domain socket":
[ssh_connection]
control_path = ~/.ssh/ansible-ssh-%%C

#When deploying with Linux OS use this control_path if you receive the 
following error "Failed to connect to the host via ssh: percent_expand: unknown 
key %C":
#[ssh_connection]
#control_path = ~/.ssh/ansbile-ssh-%%h-%%r
```


> EC2 Deployment - Updating control_path to accommodate for Linux
> ---
>
> Key: METRON-1184
> URL: https://issues.apache.org/jira/browse/METRON-1184
> Project: Metron
>  Issue Type: Improvement
>Affects Versions: 0.4.1
> Environment: ClearOS[Distro of CentOS] npm 3.10.10, node 6.11.1, 
> docker 1.12.6, mvn 3.3.9, ansible 2.2.2.0, No Vagrant)
>Reporter: ashah
>Assignee: ashah
>Priority: Minor
>  Labels: amazon, cloud
> Fix For: 0.5.0
>
>
> PR: https://github.com/apache/metron/pull/754
> For 0.4.1-rc4, using "control_path = ~/.ssh/ansible-ssh-%%C" for a Linux 
> environment ( such as ClearOS[Distro of CentOS] npm 3.10.10, node 6.11.1, 
> docker 1.12.6, mvn 3.3.9, ansible 2.2.2.0, No Vagrant) could throw the 
> following error:
> ```
> "TASK [setup] 
> ***
> fatal: [ec2-xx-yy-0-130.us-west-2.compute.amazonaws.com]: UNREACHABLE! => 
> {"changed": false, "msg": "Failed to connect to the host via ssh: 
> percent_expand: unknown key %C\r\n", "unreachable": true}" 
> ```
> This PR is to change the line to "control_path = ~/.ssh/ansbile-ssh-%%h-%%r" 
> to make amazon-ec2 also potentially deployable with Linux while preserving a 
> small path length. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] metron issue #754: METRON-1184 EC2 Deployment - Updating control_path to acc...

[as22323]

Github user as22323 commented on the issue:

https://github.com/apache/metron/pull/754
  
Could the following approach be taken?: 

In metron-deployment/amazon-ec2/README.md add two new "Errors" in the 
"Common Error Section"

1) 
# Error: ''Failed to connect to the host via ssh: percent_expand: unknown 
key %C\r\n"

This error might occur if you are deploying with Linux OS. The %C in the 
control_path is compatible with Mac OS but might not be compatible certain 
Linux operating systems.

## Solution
If you see this error update the control_path  in ansble.cfg  to the 
following. 
```
control_path = ~/.ssh/ansbile-ssh-%%h-%%r
```

2) 
# Error: ''too long for Unix domain socket\rn\n"
This error might occur if you are deploying with Mac OS.

## Solution
If you see this error when deploying with a Mac update the control_path in  
ansble.cfg to the following.
```
control_path = ~/.ssh/ansible-ssh-%%C
```

---
Update ansble.cfg to include comments: 
```
#When deploying with Mac OS use this control_path if you receive the 
following error "too long for Unix domain socket":
[ssh_connection]
control_path = ~/.ssh/ansible-ssh-%%C

#When deploying with Linux OS use this control_path if you receive the 
following error "Failed to connect to the host via ssh: percent_expand: unknown 
key %C":
#[ssh_connection]
#control_path = ~/.ssh/ansbile-ssh-%%h-%%r
```


---

[jira] [Commented] (METRON-1421) Create a SolrMetaAlertDao

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on METRON-1421:


Github user merrimanr commented on the issue:

https://github.com/apache/metron/pull/970
  
+1 from me.  Thanks @justinleet, this was a beast.


> Create a SolrMetaAlertDao
> -
>
> Key: METRON-1421
> URL: https://issues.apache.org/jira/browse/METRON-1421
> Project: Metron
>  Issue Type: Sub-task
>Reporter: Justin Leet
>Assignee: Justin Leet
>Priority: Major
>
> Create an implementation of the MetaAlertDao for Solr. This will involve 
> implementing the various MetaAlertDao methods using the SolrJ library and 
> also providing a SolrMetaAlertIntegrationTest (similar to 
> ElasticsearchMetaAlertIntegrationTest).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] metron issue #970: METRON-1421: Create a SolrMetaAlertDao

[merrimanr]

Github user merrimanr commented on the issue:

https://github.com/apache/metron/pull/970
  
+1 from me.  Thanks @justinleet, this was a beast.


---

[jira] [Commented] (METRON-1570) Downgrade Solr version to match HDP Search

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on METRON-1570:


GitHub user merrimanr opened a pull request:

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

METRON-1570: Downgrade Solr version to match HDP Search

## Contributor Comments
This PR downgrades our Solr version from 6.6.2 to 5.5.4.  The purpose of 
this change is to catch any incompatibilities with 5.5.4 at compile time rather 
than at runtime when using Solr 5.5.4.  In theory Solr client code compiled 
with 5.5.4 should work with 6.6.2.

All changes were fairly minor.  A summary includes:

- disabled Solr auto-configuration in REST
- changed Solr client instantiation to be compatible with 5.5.4
- changed Solr collection listing call to be compatible with 5.5.4
- changed Kerberos configuration to be compatible with 5.5.4
- updated the in-memory SolrComponent to be compatible with 5.5.4

I tested this in full dev with HDP Search 2.2 (Solr 5.5.4) and could not 
find any issues.  I also enabled Kerberos and everything worked as expected.

## 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:
- [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?
- [x] Have you ensured that the full suite of tests and checks have been 
executed in the root metron folder via:
  ```
  mvn -q clean integration-test install && 
dev-utilities/build-utils/verify_licenses.sh 
  ```

- [x] Have you written or updated unit tests and or integration tests to 
verify your changes?
- [x] 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:
- [x] 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/merrimanr/incubator-metron METRON-1570

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

https://github.com/apache/metron/pull/1027.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 #1027


commit 267d645b3b3da6585fbe8251bf54d47656aaff21
Author: merrimanr 
Date:   2018-05-22T20:38:09Z

initial commit




> Downgrade Solr version to match HDP Search
> --
>
> Key: METRON-1570
> URL: https://issues.apache.org/jira/browse/METRON-1570
> Project: Metron
>  Issue Type: Bug
>Reporter: Ryan Merriman
>Priority: Major
>
> We should be building and testing with the same version as HDP Search 
> (5.5.4). We need to bump our Mave

[GitHub] metron pull request #1027: METRON-1570: Downgrade Solr version to match HDP ...

[merrimanr]

GitHub user merrimanr opened a pull request:

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

METRON-1570: Downgrade Solr version to match HDP Search

## Contributor Comments
This PR downgrades our Solr version from 6.6.2 to 5.5.4.  The purpose of 
this change is to catch any incompatibilities with 5.5.4 at compile time rather 
than at runtime when using Solr 5.5.4.  In theory Solr client code compiled 
with 5.5.4 should work with 6.6.2.

All changes were fairly minor.  A summary includes:

- disabled Solr auto-configuration in REST
- changed Solr client instantiation to be compatible with 5.5.4
- changed Solr collection listing call to be compatible with 5.5.4
- changed Kerberos configuration to be compatible with 5.5.4
- updated the in-memory SolrComponent to be compatible with 5.5.4

I tested this in full dev with HDP Search 2.2 (Solr 5.5.4) and could not 
find any issues.  I also enabled Kerberos and everything worked as expected.

## 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:
- [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?
- [x] Have you ensured that the full suite of tests and checks have been 
executed in the root metron folder via:
  ```
  mvn -q clean integration-test install && 
dev-utilities/build-utils/verify_licenses.sh 
  ```

- [x] Have you written or updated unit tests and or integration tests to 
verify your changes?
- [x] 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:
- [x] 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/merrimanr/incubator-metron METRON-1570

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

https://github.com/apache/metron/pull/1027.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 #1027


commit 267d645b3b3da6585fbe8251bf54d47656aaff21
Author: merrimanr 
Date:   2018-05-22T20:38:09Z

initial commit




---

[jira] [Commented] (METRON-1421) Create a SolrMetaAlertDao

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on METRON-1421:


Github user mmiklavc commented on the issue:

https://github.com/apache/metron/pull/970
  
Given the added fix by @merrimanr, this lgtm. +1


> Create a SolrMetaAlertDao
> -
>
> Key: METRON-1421
> URL: https://issues.apache.org/jira/browse/METRON-1421
> Project: Metron
>  Issue Type: Sub-task
>Reporter: Justin Leet
>Assignee: Justin Leet
>Priority: Major
>
> Create an implementation of the MetaAlertDao for Solr. This will involve 
> implementing the various MetaAlertDao methods using the SolrJ library and 
> also providing a SolrMetaAlertIntegrationTest (similar to 
> ElasticsearchMetaAlertIntegrationTest).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] metron issue #970: METRON-1421: Create a SolrMetaAlertDao

[mmiklavc]

Github user mmiklavc commented on the issue:

https://github.com/apache/metron/pull/970
  
Given the added fix by @merrimanr, this lgtm. +1


---

[jira] [Commented] (METRON-1421) Create a SolrMetaAlertDao

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on METRON-1421:


Github user cestella commented on the issue:

https://github.com/apache/metron/pull/970
  
I'm giving this a +1 after going through the test script, great job and 
thanks for the effort.


> Create a SolrMetaAlertDao
> -
>
> Key: METRON-1421
> URL: https://issues.apache.org/jira/browse/METRON-1421
> Project: Metron
>  Issue Type: Sub-task
>Reporter: Justin Leet
>Assignee: Justin Leet
>Priority: Major
>
> Create an implementation of the MetaAlertDao for Solr. This will involve 
> implementing the various MetaAlertDao methods using the SolrJ library and 
> also providing a SolrMetaAlertIntegrationTest (similar to 
> ElasticsearchMetaAlertIntegrationTest).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] metron issue #970: METRON-1421: Create a SolrMetaAlertDao

[cestella]

Github user cestella commented on the issue:

https://github.com/apache/metron/pull/970
  
I'm giving this a +1 after going through the test script, great job and 
thanks for the effort.


---

[jira] [Commented] (METRON-1566) Alert updates are not propagated to metaalert child alerts

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on METRON-1566:


Github user asfgit closed the pull request at:

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


> Alert updates are not propagated to metaalert child alerts
> --
>
> Key: METRON-1566
> URL: https://issues.apache.org/jira/browse/METRON-1566
> Project: Metron
>  Issue Type: Bug
>Reporter: Ryan Merriman
>Priority: Major
>
> This can be reproduced as follows:
>  * Create a metaalert from an alert
>  * Update that alert with the patch endpoint
>  * The change to the alert is not reflected in the metaalert child alert



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] metron pull request #1018: METRON-1566: Alert updates are not propagated to ...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[jira] [Commented] (METRON-1184) EC2 Deployment - Updating control_path to accommodate for Linux

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on METRON-1184:


Github user JonZeolla commented on the issue:

https://github.com/apache/metron/pull/754
  
@nickwallen My similar issue in the past was spinning up full-dev (centos) 
on a centos host.  I think there's a closed PR on that somewhere.


> EC2 Deployment - Updating control_path to accommodate for Linux
> ---
>
> Key: METRON-1184
> URL: https://issues.apache.org/jira/browse/METRON-1184
> Project: Metron
>  Issue Type: Improvement
>Affects Versions: 0.4.1
> Environment: ClearOS[Distro of CentOS] npm 3.10.10, node 6.11.1, 
> docker 1.12.6, mvn 3.3.9, ansible 2.2.2.0, No Vagrant)
>Reporter: ashah
>Assignee: ashah
>Priority: Minor
>  Labels: amazon, cloud
> Fix For: 0.5.0
>
>
> PR: https://github.com/apache/metron/pull/754
> For 0.4.1-rc4, using "control_path = ~/.ssh/ansible-ssh-%%C" for a Linux 
> environment ( such as ClearOS[Distro of CentOS] npm 3.10.10, node 6.11.1, 
> docker 1.12.6, mvn 3.3.9, ansible 2.2.2.0, No Vagrant) could throw the 
> following error:
> ```
> "TASK [setup] 
> ***
> fatal: [ec2-xx-yy-0-130.us-west-2.compute.amazonaws.com]: UNREACHABLE! => 
> {"changed": false, "msg": "Failed to connect to the host via ssh: 
> percent_expand: unknown key %C\r\n", "unreachable": true}" 
> ```
> This PR is to change the line to "control_path = ~/.ssh/ansbile-ssh-%%h-%%r" 
> to make amazon-ec2 also potentially deployable with Linux while preserving a 
> small path length. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] metron issue #754: METRON-1184 EC2 Deployment - Updating control_path to acc...

[JonZeolla]

Github user JonZeolla commented on the issue:

https://github.com/apache/metron/pull/754
  
@nickwallen My similar issue in the past was spinning up full-dev (centos) 
on a centos host.  I think there's a closed PR on that somewhere.


---

[jira] [Commented] (METRON-1184) EC2 Deployment - Updating control_path to accommodate for Linux

[Ahmed Shah (JIRA)]

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

Ahmed Shah commented on METRON-1184:


According to the following, AWS is migrating to using longer resource ids which 
might be increasing the control_path length.

https://aws.amazon.com/blogs/compute/longer-resource-ids-in-2018-for-amazon-ec2-amazon-ebs-and-amazon-vpc/


Instead of trying to make one control_path that is compatible for both Linux 
and Mac could the following approach be taken?:

In 
metron-deployment/amazon-ec2/README.md
 add two new "Errors" in the "Common Error Section"

1)
Error: ''Failed to connect to the host via ssh: percent_expand: unknown key 
%C\r\n"

This error might occur if you are deploying with Linux OS. The %C in the 
control_path is compatible with Mac OS but might not be compatible with a Linux 
operating system.

Solution
If you see this error update the control_path  in ansble.cfg  to the following.
```
control_path = ~/.ssh/ansbile-ssh-%%h-%%r
```

2)
Error: ''too long for Unix domain socket\rn\n"
This error might occur if you are deploying with Mac OS.

Solution
If you see this error when deploying with a Mac update the control_path in  
ansble.cfg to the following.
```
control_path = ~/.ssh/ansible-ssh-%%C
```


---

Update ansble.cfg to include comments:


#When deploying with Mac OS use this control_path if you receive the following 
error "too long for Unix domain socket":

#[ssh_connection]

#control_path = ~/.ssh/ansible-ssh-%%C


#When deploying with Linux OS use this control_path if you receive the 
following error "Failed to connect to the host via ssh: percent_expand: unknown 
key %C":
#[ssh_connection]

#control_path = ~/.ssh/ansbile-ssh-%%h-%%r


-Ahmed



> EC2 Deployment - Updating control_path to accommodate for Linux
> ---
>
> Key: METRON-1184
> URL: https://issues.apache.org/jira/browse/METRON-1184
> Project: Metron
>  Issue Type: Improvement
>Affects Versions: 0.4.1
> Environment: ClearOS[Distro of CentOS] npm 3.10.10, node 6.11.1, 
> docker 1.12.6, mvn 3.3.9, ansible 2.2.2.0, No Vagrant)
>Reporter: ashah
>Assignee: ashah
>Priority: Minor
>  Labels: amazon, cloud
> Fix For: 0.5.0
>
>
> PR: https://github.com/apache/metron/pull/754
> For 0.4.1-rc4, using "control_path = ~/.ssh/ansible-ssh-%%C" for a Linux 
> environment ( such as ClearOS[Distro of CentOS] npm 3.10.10, node 6.11.1, 
> docker 1.12.6, mvn 3.3.9, ansible 2.2.2.0, No Vagrant) could throw the 
> following error:
> ```
> "TASK [setup] 
> ***
> fatal: [ec2-xx-yy-0-130.us-west-2.compute.amazonaws.com]: UNREACHABLE! => 
> {"changed": false, "msg": "Failed to connect to the host via ssh: 
> percent_expand: unknown key %C\r\n", "unreachable": true}" 
> ```
> This PR is to change the line to "control_path = ~/.ssh/ansbile-ssh-%%h-%%r" 
> to make amazon-ec2 also potentially deployable with Linux while preserving a 
> small path length. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (METRON-1184) EC2 Deployment - Updating control_path to accommodate for Linux

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on METRON-1184:


Github user ottobackwards commented on the issue:

https://github.com/apache/metron/pull/754
  
I don't have an EC2 to use unfortunately.  @lvets  is the only one who 
answered the call to test.  If it doesn't work on the mac, then we need a new 
jira and proposed fix I guess


> EC2 Deployment - Updating control_path to accommodate for Linux
> ---
>
> Key: METRON-1184
> URL: https://issues.apache.org/jira/browse/METRON-1184
> Project: Metron
>  Issue Type: Improvement
>Affects Versions: 0.4.1
> Environment: ClearOS[Distro of CentOS] npm 3.10.10, node 6.11.1, 
> docker 1.12.6, mvn 3.3.9, ansible 2.2.2.0, No Vagrant)
>Reporter: ashah
>Assignee: ashah
>Priority: Minor
>  Labels: amazon, cloud
> Fix For: 0.5.0
>
>
> PR: https://github.com/apache/metron/pull/754
> For 0.4.1-rc4, using "control_path = ~/.ssh/ansible-ssh-%%C" for a Linux 
> environment ( such as ClearOS[Distro of CentOS] npm 3.10.10, node 6.11.1, 
> docker 1.12.6, mvn 3.3.9, ansible 2.2.2.0, No Vagrant) could throw the 
> following error:
> ```
> "TASK [setup] 
> ***
> fatal: [ec2-xx-yy-0-130.us-west-2.compute.amazonaws.com]: UNREACHABLE! => 
> {"changed": false, "msg": "Failed to connect to the host via ssh: 
> percent_expand: unknown key %C\r\n", "unreachable": true}" 
> ```
> This PR is to change the line to "control_path = ~/.ssh/ansbile-ssh-%%h-%%r" 
> to make amazon-ec2 also potentially deployable with Linux while preserving a 
> small path length. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] metron issue #754: METRON-1184 EC2 Deployment - Updating control_path to acc...

[ottobackwards]

Github user ottobackwards commented on the issue:

https://github.com/apache/metron/pull/754
  
I don't have an EC2 to use unfortunately.  @lvets  is the only one who 
answered the call to test.  If it doesn't work on the mac, then we need a new 
jira and proposed fix I guess


---

[jira] [Commented] (METRON-1184) EC2 Deployment - Updating control_path to accommodate for Linux

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on METRON-1184:


Github user nickwallen commented on the issue:

https://github.com/apache/metron/pull/754
  
@ottobackwards Did you or anyone else happen to test this on a Mac?  I 
believe @mmiklavc runs a Mac and it is not working for him.  I am curious if 
this is working for anyone on a Mac.  


> EC2 Deployment - Updating control_path to accommodate for Linux
> ---
>
> Key: METRON-1184
> URL: https://issues.apache.org/jira/browse/METRON-1184
> Project: Metron
>  Issue Type: Improvement
>Affects Versions: 0.4.1
> Environment: ClearOS[Distro of CentOS] npm 3.10.10, node 6.11.1, 
> docker 1.12.6, mvn 3.3.9, ansible 2.2.2.0, No Vagrant)
>Reporter: ashah
>Assignee: ashah
>Priority: Minor
>  Labels: amazon, cloud
> Fix For: 0.5.0
>
>
> PR: https://github.com/apache/metron/pull/754
> For 0.4.1-rc4, using "control_path = ~/.ssh/ansible-ssh-%%C" for a Linux 
> environment ( such as ClearOS[Distro of CentOS] npm 3.10.10, node 6.11.1, 
> docker 1.12.6, mvn 3.3.9, ansible 2.2.2.0, No Vagrant) could throw the 
> following error:
> ```
> "TASK [setup] 
> ***
> fatal: [ec2-xx-yy-0-130.us-west-2.compute.amazonaws.com]: UNREACHABLE! => 
> {"changed": false, "msg": "Failed to connect to the host via ssh: 
> percent_expand: unknown key %C\r\n", "unreachable": true}" 
> ```
> This PR is to change the line to "control_path = ~/.ssh/ansbile-ssh-%%h-%%r" 
> to make amazon-ec2 also potentially deployable with Linux while preserving a 
> small path length. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] metron issue #754: METRON-1184 EC2 Deployment - Updating control_path to acc...

[nickwallen]

Github user nickwallen commented on the issue:

https://github.com/apache/metron/pull/754
  
@ottobackwards Did you or anyone else happen to test this on a Mac?  I 
believe @mmiklavc runs a Mac and it is not working for him.  I am curious if 
this is working for anyone on a Mac.  


---