[jira] [Created] (METRON-780) NarClassloader based on VFSClassloader

[Otto Fowler (JIRA)]

Otto Fowler created METRON-780:
--

 Summary: NarClassloader based on VFSClassloader
 Key: METRON-780
 URL: https://issues.apache.org/jira/browse/METRON-780
 Project: Metron
  Issue Type: Sub-task
Reporter: Otto Fowler
Assignee: Otto Fowler


The NarClassloader will be refactored to be based on the VFSClassloader.

It is important that this be done in a way that both the existing file paths 
and other paths such as hdfs:// paths still work.

IE:  the existing unit tests ( file based ) should still work



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (METRON-781) Create Tests and Support for testing HDFS Nar unpacking and loading

[Otto Fowler (JIRA)]

Otto Fowler created METRON-781:
--

 Summary: Create Tests and Support for testing HDFS Nar unpacking 
and loading
 Key: METRON-781
 URL: https://issues.apache.org/jira/browse/METRON-781
 Project: Metron
  Issue Type: Sub-task
Reporter: Otto Fowler
Assignee: Otto Fowler


* The project needs support for the integration testing harness for HDFS
* We need an integration test that sets up hdfs and the nar dirs and runs the 
same narunpacker tests but from hdfs
* We need to refactor the FileUtils such that we can both use the static and 
have interface based implementations.  HDFS in VFS is READ_ONLY, so unpacking 
will not work.  This refactoring will make it possible to inject an HDFS File 
utils implementation that using the HDFS FileSystem and overrides any write or 
creation code



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (METRON-783) The Nar-Id and Nar-Group and File extension should be configurable in the Nar System

[Otto Fowler (JIRA)]

Otto Fowler created METRON-783:
--

 Summary: The Nar-Id and Nar-Group and File extension should be 
configurable in the Nar System
 Key: METRON-783
 URL: https://issues.apache.org/jira/browse/METRON-783
 Project: Metron
  Issue Type: Sub-task
Reporter: Otto Fowler
Assignee: Otto Fowler


These hard coded package metadata names are NIFI and nar specific and should be 
configurable, as the maven plugin will be able to set these as well.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (METRON-787) Fork and Adapt the Nifi Maven Nar Plugin

[Otto Fowler (JIRA)]

Otto Fowler created METRON-787:
--

 Summary:  Fork and Adapt the Nifi Maven Nar Plugin
 Key: METRON-787
 URL: https://issues.apache.org/jira/browse/METRON-787
 Project: Metron
  Issue Type: Sub-task
Reporter: Otto Fowler
Assignee: Otto Fowler


* rebrand it to PAR
* expose properties to allow configuration of metadata and file extension


- I am not sure how we will host? it will need to be deployed on the build 
machine to build nars so.




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (METRON-776) Improved Elasticsearch Defaults

[David M. Lyle (JIRA)]

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

David M. Lyle updated METRON-776:
-
Affects Version/s: (was: 0.3.2)
   0.3.1

> Improved Elasticsearch Defaults 
> 
>
> Key: METRON-776
> URL: https://issues.apache.org/jira/browse/METRON-776
> Project: Metron
>  Issue Type: Improvement
>Affects Versions: 0.3.1
>Reporter: David M. Lyle
>
> Elasticsearch will perform slowly with our defaults on a 4 node Elasticsearch 
> index driven by the stub sensors. Optimize the defaults for better 
> performance.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (METRON-785) Integration tests for classloading and instantiation from HDFS

[Otto Fowler (JIRA)]

Otto Fowler created METRON-785:
--

 Summary: Integration tests for classloading and instantiation from 
HDFS
 Key: METRON-785
 URL: https://issues.apache.org/jira/browse/METRON-785
 Project: Metron
  Issue Type: Sub-task
Reporter: Otto Fowler
Assignee: Otto Fowler


The nifi nar system is short on tests, we need to add more



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (METRON-786) Rename from NAR to PAR

[Otto Fowler (JIRA)]

Otto Fowler created METRON-786:
--

 Summary: Rename from NAR to PAR
 Key: METRON-786
 URL: https://issues.apache.org/jira/browse/METRON-786
 Project: Metron
  Issue Type: Sub-task
Reporter: Otto Fowler
Assignee: Otto Fowler


Plugin ARchives



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (METRON-777) Create a plugin system for Metron based on 'NAR'

[Otto Fowler (JIRA)]

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

Otto Fowler updated METRON-777:
---
Description: 
The success of the Metron project will be greatly dependent on community 
participation, and with that the ability to adapt and extend Metron without 
having to maintain a fork of the project.

As organizations and individuals look to extend the Metron system with custom 
parsers, enrichments, and stellar functions that may be proprietary in nature, 
the ability to develop and deploy these extensions outside the Metron code base 
is critically important.

To that end, and after community discussion and proposal we create or formalize 
the 'plugin' development story in Metron.  

The proposal is to adapt the Apache Nifi NAR system for use in Metron.  This 
will provide the system with:
* archetype(s) for developer projects and independent development
* defined packaging and metadata for 'plugin' products
* loading and instantiation with classloader isolation capabilities
* removing the necessity for shading plugin jars

These capabilities will also enable other features, such as plugin lifecycle, 
plugin configuration+redeployment, and other things.
The plugin archetypes and their installation will be a followon

  was:
The success of the Metron project will be greatly dependent on community 
participation, and with that the ability to adapt and extend Metron without 
having to maintain a fork of the project.

As organizations and individuals look to extend the Metron system with custom 
parsers, enrichments, and stellar functions that may be proprietary in nature, 
the ability to develop and deploy these extensions outside the Metron code base 
is critically important.

To that end, and after community discussion and proposal we create or formalize 
the 'plugin' development story in Metron.  

The proposal is to adapt the Apache Nifi NAR system for use in Metron.  This 
will provide the system with:
* archetype(s) for developer projects and independent development
* defined packaging and metadata for 'plugin' products
* loading and instantiation with classloader isolation capabilities
* removing the necessity for shading plugin jars

These capabilities will also enable other features, such as plugin lifecycle, 
plugin configuration+redeployment, and other things.



> Create a plugin system for Metron based on 'NAR'
> 
>
> Key: METRON-777
> URL: https://issues.apache.org/jira/browse/METRON-777
> Project: Metron
>  Issue Type: New Feature
>Reporter: Otto Fowler
>Assignee: Otto Fowler
>
> The success of the Metron project will be greatly dependent on community 
> participation, and with that the ability to adapt and extend Metron without 
> having to maintain a fork of the project.
> As organizations and individuals look to extend the Metron system with custom 
> parsers, enrichments, and stellar functions that may be proprietary in 
> nature, the ability to develop and deploy these extensions outside the Metron 
> code base is critically important.
> To that end, and after community discussion and proposal we create or 
> formalize the 'plugin' development story in Metron.  
> The proposal is to adapt the Apache Nifi NAR system for use in Metron.  This 
> will provide the system with:
> * archetype(s) for developer projects and independent development
> * defined packaging and metadata for 'plugin' products
> * loading and instantiation with classloader isolation capabilities
> * removing the necessity for shading plugin jars
> These capabilities will also enable other features, such as plugin lifecycle, 
> plugin configuration+redeployment, and other things.
> The plugin archetypes and their installation will be a followon



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (METRON-777) Create a plugin system for Metron based on M

[Otto Fowler (JIRA)]

Otto Fowler created METRON-777:
--

 Summary: Create a plugin system for Metron based on M
 Key: METRON-777
 URL: https://issues.apache.org/jira/browse/METRON-777
 Project: Metron
  Issue Type: New Feature
Reporter: Otto Fowler
Assignee: Otto Fowler


The success of the Metron project will be greatly dependent on community 
participation, and with that the ability to adapt and extend Metron without 
having to maintain a fork of the project.

As organizations and individuals look to extend the Metron system with custom 
parsers, enrichments, and stellar functions that may be proprietary in nature, 
the ability to develop and deploy these extensions outside the Metron code base 
is critically important.

To that end, and after community discussion and proposal we create or formalize 
the 'plugin' development story in Metron.  

The proposal is to adapt the Apache Nifi NAR system for use in Metron.  This 
will provide the system with:
* archetype(s) for developer projects and independent development
* defined packaging and metadata for 'plugin' products
* loading and instantiation with classloader isolation capabilities
* removing the necessity for shading plugin jars

These capabilities will also enable other features, such as plugin lifecycle, 
plugin configuration+redeployment, and other things.




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (METRON-778) Create plugin module under Metron from nifi-nar-utils

[Otto Fowler (JIRA)]

Otto Fowler created METRON-778:
--

 Summary: Create plugin module under Metron from nifi-nar-utils
 Key: METRON-778
 URL: https://issues.apache.org/jira/browse/METRON-778
 Project: Metron
  Issue Type: Sub-task
Reporter: Otto Fowler
Assignee: Otto Fowler


Create a new top level module in Metron.  Although it is a child of the metron 
pom, we do not want to have any dependencies on Metron modules.

This effort is to create the project, set it up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (METRON-775) Metron service restart fails when services are stopped.

[David M. Lyle (JIRA)]

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

David M. Lyle updated METRON-775:
-
Affects Version/s: (was: 0.3.2)
   0.3.1

> Metron service restart fails when services are stopped.
> ---
>
> Key: METRON-775
> URL: https://issues.apache.org/jira/browse/METRON-775
> Project: Metron
>  Issue Type: Bug
>Affects Versions: 0.3.1
>Reporter: David M. Lyle
>
> Restarting Metron services from Ambari will fail when the services are 
> stopped.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (METRON-774) enrichment.properties changes in Ambari are not honored

[David M. Lyle (JIRA)]

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

David M. Lyle updated METRON-774:
-
Affects Version/s: (was: 0.3.2)
   0.3.1

> enrichment.properties changes in Ambari are not honored
> ---
>
> Key: METRON-774
> URL: https://issues.apache.org/jira/browse/METRON-774
> Project: Metron
>  Issue Type: Bug
>Affects Versions: 0.3.1
>Reporter: David M. Lyle
>
> Currently, enrichment_master.py only calls the configure method during 
> install. As a result, many of the changes to advanced config will not 
> propagate on restart. Relocate the call to the start method. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (METRON-787) Fork and Adapt the Nifi Maven Nar Plugin

[Otto Fowler (JIRA)]

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

Otto Fowler updated METRON-787:
---
Description: 
If we cannot PR it and get a release
* rebrand it to PAR
* expose properties to allow configuration of metadata and file extension

Else

* expose properties to all configuration of the metadata and file extension

- I am not sure how we will host? it will need to be deployed on the build 
machine to build nars so.
- I am still going to look into just putting a PR up against the nifi plugin, 
if they take it and deploy
then we can just use that


  was:
* rebrand it to PAR
* expose properties to allow configuration of metadata and file extension


- I am not sure how we will host? it will need to be deployed on the build 
machine to build nars so.
- I am still going to look into just putting a PR up against the nifi plugin, 
if they take it and deploy
then we can just use that



>  Fork and Adapt the Nifi Maven Nar Plugin
> -
>
> Key: METRON-787
> URL: https://issues.apache.org/jira/browse/METRON-787
> Project: Metron
>  Issue Type: Sub-task
>Reporter: Otto Fowler
>Assignee: Otto Fowler
>
> If we cannot PR it and get a release
> * rebrand it to PAR
> * expose properties to allow configuration of metadata and file extension
> Else
> * expose properties to all configuration of the metadata and file extension
> - I am not sure how we will host? it will need to be deployed on the build 
> machine to build nars so.
> - I am still going to look into just putting a PR up against the nifi plugin, 
> if they take it and deploy
> then we can just use that



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (METRON-790) Produce new test 'Pars' with new metadata and integrate

[Otto Fowler (JIRA)]

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

Otto Fowler reassigned METRON-790:
--

Assignee: Otto Fowler

> Produce new test 'Pars' with new metadata and integrate
> ---
>
> Key: METRON-790
> URL: https://issues.apache.org/jira/browse/METRON-790
> Project: Metron
>  Issue Type: Sub-task
>Reporter: Otto Fowler
>Assignee: Otto Fowler
>
> * create some pars for tests to replace the current nars.
> * integrate them with the tests
> * use new metadata



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (METRON-790) Produce new test 'Pars' with new metadata and integrate

[Otto Fowler (JIRA)]

Otto Fowler created METRON-790:
--

 Summary: Produce new test 'Pars' with new metadata and integrate
 Key: METRON-790
 URL: https://issues.apache.org/jira/browse/METRON-790
 Project: Metron
  Issue Type: Sub-task
Reporter: Otto Fowler


* create some pars for tests to replace the current nars.
* integrate them with the tests
* use new metadata



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (METRON-777) Create a plugin system for Metron based on 'NAR'

[Otto Fowler (JIRA)]

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

Otto Fowler updated METRON-777:
---
Summary: Create a plugin system for Metron based on 'NAR'  (was: Create a 
plugin system for Metron based on M)

> Create a plugin system for Metron based on 'NAR'
> 
>
> Key: METRON-777
> URL: https://issues.apache.org/jira/browse/METRON-777
> Project: Metron
>  Issue Type: New Feature
>Reporter: Otto Fowler
>Assignee: Otto Fowler
>
> The success of the Metron project will be greatly dependent on community 
> participation, and with that the ability to adapt and extend Metron without 
> having to maintain a fork of the project.
> As organizations and individuals look to extend the Metron system with custom 
> parsers, enrichments, and stellar functions that may be proprietary in 
> nature, the ability to develop and deploy these extensions outside the Metron 
> code base is critically important.
> To that end, and after community discussion and proposal we create or 
> formalize the 'plugin' development story in Metron.  
> The proposal is to adapt the Apache Nifi NAR system for use in Metron.  This 
> will provide the system with:
> * archetype(s) for developer projects and independent development
> * defined packaging and metadata for 'plugin' products
> * loading and instantiation with classloader isolation capabilities
> * removing the necessity for shading plugin jars
> These capabilities will also enable other features, such as plugin lifecycle, 
> plugin configuration+redeployment, and other things.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (METRON-784) The required frameworks should be configurable

[Otto Fowler (JIRA)]

Otto Fowler created METRON-784:
--

 Summary: The required frameworks should be configurable
 Key: METRON-784
 URL: https://issues.apache.org/jira/browse/METRON-784
 Project: Metron
  Issue Type: Sub-task
Reporter: Otto Fowler
Assignee: Otto Fowler


The nifi nar system has rules where it looks for the jetty framework and the 
nifi-framework specifically.

This should be configurable such that you can state what frameworks you require.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (METRON-786) Rename from NAR to PAR Code

[Otto Fowler (JIRA)]

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

Otto Fowler updated METRON-786:
---
Summary: Rename from NAR to PAR Code  (was: Rename from NAR to PAR)

> Rename from NAR to PAR Code
> ---
>
> Key: METRON-786
> URL: https://issues.apache.org/jira/browse/METRON-786
> Project: Metron
>  Issue Type: Sub-task
>Reporter: Otto Fowler
>Assignee: Otto Fowler
>
> Plugin ARchives



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (METRON-772) Dummy defect - testing

[Jon Zeolla (JIRA)]

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

Jon Zeolla reassigned METRON-772:
-

Assignee: Jon Zeolla

Self-assign

> Dummy defect - testing
> --
>
> Key: METRON-772
> URL: https://issues.apache.org/jira/browse/METRON-772
> Project: Metron
>  Issue Type: Bug
>Reporter: Anand Subramanian
>Assignee: Jon Zeolla
>Priority: Trivial
>
> This dummy defect is created to test 
> [INFRA-13660|https://issues.apache.org/jira/browse/INFRA-13660].



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (METRON-766) Release 0.3.1

[ASF GitHub Bot (JIRA)]

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

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

Github user cestella commented on the issue:

https://github.com/apache/incubator-metron/pull/477
  
@merrimanr Any ideas on the cause of that one or a reasonable fix for it?


> Release 0.3.1
> -
>
> Key: METRON-766
> URL: https://issues.apache.org/jira/browse/METRON-766
> Project: Metron
>  Issue Type: Task
>Reporter: Casey Stella
>Assignee: Casey Stella
>
> * Remove the 0.3.0 bits in svn from dist
> * Add the 0.3.1 bits from RC5 to dist
> * Update the webpage with the 0.3.1 release



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (METRON-766) Release 0.3.1

[ASF GitHub Bot (JIRA)]

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

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

GitHub user cestella reopened a pull request:

https://github.com/apache/incubator-metron/pull/477

METRON-766: Release 0.3.1

* Remove the 0.3.0 bits in svn from release
* Add the 0.3.1 bits from RC5 to release
* Update the webpage with the 0.3.1 release



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

$ git pull https://github.com/cestella/incubator-metron 
metron_0.3.1_release_announce

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

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


commit 19b9850c4b2e8f00dfccc026a7d6f46f808eba47
Author: cstella 
Date:   2017-03-16T15:22:28Z

Release 0.3.1 website update.

commit 2024da8cb1ceb7ef644b3c63e47214a94ab7a44b
Author: cstella 
Date:   2017-03-16T22:12:28Z

Extra MD5 link.  bo




> Release 0.3.1
> -
>
> Key: METRON-766
> URL: https://issues.apache.org/jira/browse/METRON-766
> Project: Metron
>  Issue Type: Task
>Reporter: Casey Stella
>Assignee: Casey Stella
>
> * Remove the 0.3.0 bits in svn from dist
> * Add the 0.3.1 bits from RC5 to dist
> * Update the webpage with the 0.3.1 release



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (METRON-766) Release 0.3.1

[ASF GitHub Bot (JIRA)]

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

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

Github user cestella closed the pull request at:

https://github.com/apache/incubator-metron/pull/477


> Release 0.3.1
> -
>
> Key: METRON-766
> URL: https://issues.apache.org/jira/browse/METRON-766
> Project: Metron
>  Issue Type: Task
>Reporter: Casey Stella
>Assignee: Casey Stella
>
> * Remove the 0.3.0 bits in svn from dist
> * Add the 0.3.1 bits from RC5 to dist
> * Update the webpage with the 0.3.1 release



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (METRON-766) Release 0.3.1

[ASF GitHub Bot (JIRA)]

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

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

Github user cestella commented on the issue:

https://github.com/apache/incubator-metron/pull/477
  
I'm going to have to kick travis again.  It looks like that Kafka test in 
the REST API has a number of intermittent issues.  Seeing this exception:
```
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 8.514 sec 
<<< FAILURE! - in 
org.apache.metron.rest.controller.KafkaControllerIntegrationTest
test(org.apache.metron.rest.controller.KafkaControllerIntegrationTest)  
Time elapsed: 8.415 sec  <<< FAILURE!
java.lang.AssertionError: Status expected:<200> but was:<404>
at 
org.springframework.test.util.AssertionErrors.fail(AssertionErrors.java:54)
at 
org.springframework.test.util.AssertionErrors.assertEquals(AssertionErrors.java:81)
at 
org.springframework.test.web.servlet.result.StatusResultMatchers$10.match(StatusResultMatchers.java:664)
at 
org.springframework.test.web.servlet.MockMvc$1.andExpect(MockMvc.java:171)
at 
org.apache.metron.rest.controller.KafkaControllerIntegrationTest.test(KafkaControllerIntegrationTest.java:173)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at 
org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:75)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at 
org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:86)
at 
org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:84)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:252)
at 
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:94)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at 
org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
at 
org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:70)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at 
org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:191)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
```


> Release 0.3.1
> -
>
> Key: METRON-766
> URL: https://issues.apache.org/jira/browse/METRON-766
> Project: Metron
>  Issue Type: Task
>Reporter: Casey Stella
>Assignee: Casey Stella
>
> * Remove the 0.3.0 bits in svn from dist
> * Add the 0.3.1 bits from RC5 to dist
> * Update the webpage with the 0.3.1 release



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (METRON-770) Unable to Launch Fastcapa Test Environment

[ASF GitHub Bot (JIRA)]

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

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

Github user nickwallen commented on the issue:

https://github.com/apache/incubator-metron/pull/480
  
No worries. I missed it too.


> Unable to Launch Fastcapa Test Environment
> --
>
> Key: METRON-770
> URL: https://issues.apache.org/jira/browse/METRON-770
> Project: Metron
>  Issue Type: Bug
>Reporter: Nick Allen
>Assignee: Nick Allen
>
> Unable to launch the Fastcapa test environment.  Errors out during launch 
> with the following error.
> {code}
> TASK [ambari_gather_facts : Ask Ambari: metron_hosts] 
> **
> fatal: [source]: FAILED! => {"failed": true, "msg": "ERROR! 'dict object' has 
> no attribute 'ambari_master'"}
> PLAY RECAP 
> *
> source : ok=20   changed=15   unreachable=0failed=1
> Ansible failed to complete successfully. Any error output should be
> visible above. Please fix these errors and try again.
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (METRON-670) Monit Incorrectly Reports Status

[ASF GitHub Bot (JIRA)]

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

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

Github user nickwallen closed the pull request at:

https://github.com/apache/incubator-metron/pull/422


> Monit Incorrectly Reports Status
> 
>
> Key: METRON-670
> URL: https://issues.apache.org/jira/browse/METRON-670
> Project: Metron
>  Issue Type: Bug
>Reporter: Nick Allen
>Assignee: Nick Allen
> Fix For: 0.3.1
>
>
> In a constrained environment, like 'Quick Dev', Monit will often incorrectly 
> report the status of a Metron topology.  This occurs when the environment is 
> under load and a query of topology status exceeds the default timeout of 30 
> seconds.  Need to add a parameter so that the timeout for a status check can 
> be extended under these conditions.  This was previously done for starting 
> and stopping a topology, but not for a status checks.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (METRON-670) Monit Incorrectly Reports Status

[ASF GitHub Bot (JIRA)]

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

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

Github user nickwallen commented on the issue:

https://github.com/apache/incubator-metron/pull/422
  
No longer needed.


> Monit Incorrectly Reports Status
> 
>
> Key: METRON-670
> URL: https://issues.apache.org/jira/browse/METRON-670
> Project: Metron
>  Issue Type: Bug
>Reporter: Nick Allen
>Assignee: Nick Allen
> Fix For: 0.3.1
>
>
> In a constrained environment, like 'Quick Dev', Monit will often incorrectly 
> report the status of a Metron topology.  This occurs when the environment is 
> under load and a query of topology status exceeds the default timeout of 30 
> seconds.  Need to add a parameter so that the timeout for a status check can 
> be extended under these conditions.  This was previously done for starting 
> and stopping a topology, but not for a status checks.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (METRON-766) Release 0.3.1

[ASF GitHub Bot (JIRA)]

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

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

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-metron/pull/477


> Release 0.3.1
> -
>
> Key: METRON-766
> URL: https://issues.apache.org/jira/browse/METRON-766
> Project: Metron
>  Issue Type: Task
>Reporter: Casey Stella
>Assignee: Casey Stella
>
> * Remove the 0.3.0 bits in svn from dist
> * Add the 0.3.1 bits from RC5 to dist
> * Update the webpage with the 0.3.1 release



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (METRON-772) Dummy defect - testing

[Jon Zeolla (JIRA)]

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

Jon Zeolla edited comment on METRON-772 at 3/17/17 1:55 PM:


Close (and thus INFRA-13660) appears to have been successful.


was (Author: zeo...@gmail.com):
Close (and thus IFNRA-13660) appears to have been successful.

> Dummy defect - testing
> --
>
> Key: METRON-772
> URL: https://issues.apache.org/jira/browse/METRON-772
> Project: Metron
>  Issue Type: Bug
>Reporter: Anand Subramanian
>Assignee: Jon Zeolla
>Priority: Trivial
>
> This dummy defect is created to test 
> [INFRA-13660|https://issues.apache.org/jira/browse/INFRA-13660].



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (METRON-766) Release 0.3.1

[ASF GitHub Bot (JIRA)]

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

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

Github user cestella commented on the issue:

https://github.com/apache/incubator-metron/pull/477
  
I created https://issues.apache.org/jira/browse/METRON-773 to track this 
most recent issue.


> Release 0.3.1
> -
>
> Key: METRON-766
> URL: https://issues.apache.org/jira/browse/METRON-766
> Project: Metron
>  Issue Type: Task
>Reporter: Casey Stella
>Assignee: Casey Stella
>
> * Remove the 0.3.0 bits in svn from dist
> * Add the 0.3.1 bits from RC5 to dist
> * Update the webpage with the 0.3.1 release



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (METRON-773) Intermittent unit test errors in the KafkaControllerIntegrationTest

[Justin Leet (JIRA)]

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

Justin Leet commented on METRON-773:


I've also seen this in the fixes for the site build, intermittently.

https://travis-ci.org/justinleet/incubator-metron/builds/209355250

> Intermittent unit test errors in the KafkaControllerIntegrationTest
> ---
>
> Key: METRON-773
> URL: https://issues.apache.org/jira/browse/METRON-773
> Project: Metron
>  Issue Type: Bug
>Reporter: Casey Stella
>Assignee: Casey Stella
>
> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 8.514 sec <<< 
> FAILURE! - in org.apache.metron.rest.controller.KafkaControllerIntegrationTest
> test(org.apache.metron.rest.controller.KafkaControllerIntegrationTest)  Time 
> elapsed: 8.415 sec  <<< FAILURE!
> java.lang.AssertionError: Status expected:<200> but was:<404>
>   at 
> org.springframework.test.util.AssertionErrors.fail(AssertionErrors.java:54)
>   at 
> org.springframework.test.util.AssertionErrors.assertEquals(AssertionErrors.java:81)
>   at 
> org.springframework.test.web.servlet.result.StatusResultMatchers$10.match(StatusResultMatchers.java:664)
>   at 
> org.springframework.test.web.servlet.MockMvc$1.andExpect(MockMvc.java:171)
>   at 
> org.apache.metron.rest.controller.KafkaControllerIntegrationTest.test(KafkaControllerIntegrationTest.java:173)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:483)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:75)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at 
> org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:86)
>   at 
> org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:84)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>   at 
> org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:252)
>   at 
> org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:94)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>   at 
> org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)
>   at 
> org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:70)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>   at 
> org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:191)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (METRON-774) enrichment.properties changes in Ambari are not honored

[David M. Lyle (JIRA)]

David M. Lyle created METRON-774:


 Summary: enrichment.properties changes in Ambari are not honored
 Key: METRON-774
 URL: https://issues.apache.org/jira/browse/METRON-774
 Project: Metron
  Issue Type: Bug
Reporter: David M. Lyle


Currently, enrichment_master.py only calls the configure method during install. 
As a result, many of the changes to advanced config will not propagate on 
restart. Relocate the call to the start method. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (METRON-774) enrichment.properties changes in Ambari are not honored

[David M. Lyle (JIRA)]

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

David M. Lyle updated METRON-774:
-
Affects Version/s: 0.3.2

> enrichment.properties changes in Ambari are not honored
> ---
>
> Key: METRON-774
> URL: https://issues.apache.org/jira/browse/METRON-774
> Project: Metron
>  Issue Type: Bug
>Affects Versions: 0.3.2
>Reporter: David M. Lyle
>
> Currently, enrichment_master.py only calls the configure method during 
> install. As a result, many of the changes to advanced config will not 
> propagate on restart. Relocate the call to the start method. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (METRON-776) Improved Elasticsearch Defaults

[David M. Lyle (JIRA)]

David M. Lyle created METRON-776:


 Summary: Improved Elasticsearch Defaults 
 Key: METRON-776
 URL: https://issues.apache.org/jira/browse/METRON-776
 Project: Metron
  Issue Type: Improvement
Reporter: David M. Lyle


Elasticsearch will perform slowly with our defaults on a 4 node Elasticsearch 
index driven by the stub sensors. Optimize the defaults for better performance.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (METRON-775) Metron service restart fails when services are stopped.

[David M. Lyle (JIRA)]

David M. Lyle created METRON-775:


 Summary: Metron service restart fails when services are stopped.
 Key: METRON-775
 URL: https://issues.apache.org/jira/browse/METRON-775
 Project: Metron
  Issue Type: Bug
Reporter: David M. Lyle


Restarting Metron services from Ambari will fail when the services are stopped.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)