GitHub user ottobackwards opened a pull request:
https://github.com/apache/metron/pull/627
METRON-1007 ambari integration for metron-management
This pr integrates the metron-management jar file, and the stellar
management functions it contains with the ambari installation, thus
GitHub user justinleet reopened a pull request:
https://github.com/apache/metron/pull/624
[DO NOT MERGE] METRON-1004: Travis CI - Job Exceeded Maximum Time Limit
## Contributor Comments
Given that Apache travis fails more often, I'm using this PR to hopefully
hit the skidoo
Github user JonZeolla commented on a diff in the pull request:
https://github.com/apache/metron/pull/627#discussion_r124873582
--- Diff: metron-deployment/packaging/docker/rpm-docker/SPECS/metron.spec
---
@@ -409,6 +428,7 @@ chkconfig --del metron-management-ui
#
Github user justinleet commented on a diff in the pull request:
https://github.com/apache/metron/pull/624#discussion_r124875780
--- Diff:
metron-platform/metron-elasticsearch/src/test/java/org/apache/metron/elasticsearch/integration/components/ElasticSearchComponent.java
---
@@
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/620
Here's an idea to get us started. A search request could look like:
```
{
"query": "ip_src_addr:192.168.66.1",
"from": 0,
"size": 25,
"sort": [
{
GitHub user JonZeolla reopened a pull request:
https://github.com/apache/metron/pull/586
METRON-508 Expand Elasticsearch templates to support the standard bro logs
## Contributor Comments
This PR makes it easier for someone with an existing bro install to send
some of their log
Github user JonZeolla closed the pull request at:
https://github.com/apache/metron/pull/586
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user JonZeolla commented on the issue:
https://github.com/apache/metron/pull/586
Last try before I merge in #624 and make it a dependancy.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
GitHub user JonZeolla reopened a pull request:
https://github.com/apache/metron/pull/586
METRON-508 Expand Elasticsearch templates to support the standard bro logs
## Contributor Comments
This PR makes it easier for someone with an existing bro install to send
some of their log
Github user JonZeolla closed the pull request at:
https://github.com/apache/metron/pull/586
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user merrimanr commented on a diff in the pull request:
https://github.com/apache/metron/pull/624#discussion_r124869167
--- Diff:
metron-platform/metron-elasticsearch/src/test/java/org/apache/metron/elasticsearch/integration/components/ElasticSearchComponent.java
---
@@
Github user justinleet closed the pull request at:
https://github.com/apache/metron/pull/624
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user justinleet reopened a pull request:
https://github.com/apache/metron/pull/624
[DO NOT MERGE] METRON-1004: Travis CI - Job Exceeded Maximum Time Limit
## Contributor Comments
This PR cleans up and speeds up various issues we've seen on Travis.
- This should
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/530
Ok, I was getting ready to bail on this for the day but couldn't stop. I
tried one more thing - setting the maven-archetype-plugin version to **2.4**
and it works as expected. Something must be
+1 (Binding)
* Verified Keys
* Verified mvn clean install completed successfully
* Verified AWS install of core via Mpack
29.06.2017, 09:14, "Justin Leet" :
> +1 (Non-binding)
>
> * Verified Keys
> * Verified mvn clean install completed successfully
> * Ran full dev: saw
Github user merrimanr commented on a diff in the pull request:
https://github.com/apache/metron/pull/624#discussion_r124927666
--- Diff:
metron-interface/metron-rest/src/test/java/org/apache/metron/rest/controller/KafkaControllerIntegrationTest.java
---
@@ -61,6 +62,7 @@
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/530
I'm ok with that, I would feel better if we got a tie breaking opinion
though.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
GitHub user justinleet reopened a pull request:
https://github.com/apache/metron/pull/624
[DO NOT MERGE] METRON-1004: Travis CI - Job Exceeded Maximum Time Limit
## Contributor Comments
This PR cleans up and speeds up various issues we've seen on Travis.
- This should
Github user justinleet closed the pull request at:
https://github.com/apache/metron/pull/624
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user justinleet closed the pull request at:
https://github.com/apache/metron/pull/624
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/624#discussion_r124921605
--- Diff:
metron-interface/metron-rest/src/test/java/org/apache/metron/rest/controller/KafkaControllerIntegrationTest.java
---
@@ -148,6 +150,15 @@ public
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/530
@mmiklavc can you comment with what your pom looks like now?
Why does 3.0 work on my machine though.
---
If your project is set up for it, you can reply to this email and have your
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/530
@ottobackwards removing the extra project element allows me to build the
project now. However, I'm still unable to use the archetype. It neither shows
up in the local catalog listing nor allows me
Github user justinleet commented on a diff in the pull request:
https://github.com/apache/metron/pull/624#discussion_r124922704
--- Diff:
metron-interface/metron-rest/src/test/java/org/apache/metron/rest/controller/KafkaControllerIntegrationTest.java
---
@@ -61,6 +62,7 @@
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/624
Most recent commits attempt to fix what appears to be a preexisting
intermittent test issue regarding Kafka.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/624#discussion_r124921122
--- Diff:
metron-interface/metron-rest/src/test/java/org/apache/metron/rest/controller/KafkaControllerIntegrationTest.java
---
@@ -61,6 +62,7 @@
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/624#discussion_r124922443
--- Diff:
metron-interface/metron-rest/src/test/java/org/apache/metron/rest/controller/KafkaControllerIntegrationTest.java
---
@@ -148,6 +150,15 @@ public
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/530
Archetype plugin version is the only change
```
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
GitHub user JonZeolla reopened a pull request:
https://github.com/apache/metron/pull/586
METRON-508 Expand Elasticsearch templates to support the standard bro logs
## Contributor Comments
This PR makes it easier for someone with an existing bro install to send
some of their log
Github user JonZeolla closed the pull request at:
https://github.com/apache/metron/pull/586
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user ottobackwards opened a pull request:
https://github.com/apache/metron/pull/626
METRON-947 [DO NOT MERGE UNTIL METRON-942] Stellar Management Function for
Metron Parser Extension Configurations
METRON-777 adds the Metron Extension capability, the default parsers as
+1 (Non-binding)
* Verified Keys
* Verified mvn clean install completed successfully
* Ran full dev: saw data flow through, ran a couple of the REST APIs, and
opened up and clicked through a bit of the Management API.
* Examined site-book and didn't see any issues
On Thu, Jun 29, 2017 at 11:46
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/624
Oh, we should also spin this up on full-dev and ensure that any of the
changes to the pom files didn't screw anything up.
---
If your project is set up for it, you can reply to this email and have
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/624
The latest commit moves to a VM instead of using a container during the
Travis build. Testing on local Travis, this seemed to produce more consistent
results that didn't have the same wide
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/624#discussion_r124842566
--- Diff:
metron-platform/metron-parsers/src/test/java/org/apache/metron/parsers/integration/ParserDriver.java
---
@@ -0,0 +1,168 @@
+/**
--- End
Github user justinleet closed the pull request at:
https://github.com/apache/metron/pull/624
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/624#discussion_r124821164
--- Diff:
metron-platform/metron-parsers/src/test/java/org/apache/metron/parsers/integration/ParserDriver.java
---
@@ -0,0 +1,168 @@
+/**
--- End
+1 (binding)
* Verified keys
* Verified mvn build
* Verified unit and integration tests run
* Verified license check runs
* Verified fulldev spun up with smoketest
On Wed, Jun 28, 2017 at 8:10 PM, Anand Subramanian <
asubraman...@hortonworks.com> wrote:
> +1 (non-binding)
>
> * Brought up Metron
Github user JonZeolla commented on the issue:
https://github.com/apache/metron/pull/586
@nickwallen @justinleet Can I get a quick review of my recent changes
before I merge? Mostly focused on how I approached documenting the template,
but feel free to comment on anything.
I
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/624
I'm spinning it up now
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/624#discussion_r124821374
--- Diff:
metron-platform/metron-parsers/src/test/java/org/apache/metron/parsers/integration/ParserDriver.java
---
@@ -0,0 +1,168 @@
+/**
--- End
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/624
The commits `6824ca9` through `1c98ae4` above represent the following:
* `ProfilerHBaseClientTest` (using mock HTable rather than hbase)
* `HBaseClientTest` (deletes contents, rather than
Github user ottobackwards commented on a diff in the pull request:
https://github.com/apache/metron/pull/530#discussion_r124780191
--- Diff:
Github user ottobackwards commented on a diff in the pull request:
https://github.com/apache/metron/pull/530#discussion_r124779193
--- Diff: metron-maven-archetypes/README.md ---
@@ -0,0 +1,56 @@
+# Metron Maven Archetypes
+
+These are [Apache Maven
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/624
travis passed. See https://travis-ci.org/apache/metron/builds/248356870
I'm going to kick it up and down a few times. Hopefully it'll start
showing here.
---
If your project is set up
GitHub user justinleet reopened a pull request:
https://github.com/apache/metron/pull/624
[DO NOT MERGE] METRON-1004: Travis CI - Job Exceeded Maximum Time Limit
## Contributor Comments
Given that Apache travis fails more often, I'm using this PR to hopefully
hit the skidoo
Github user mmiklavc commented on a diff in the pull request:
https://github.com/apache/metron/pull/530#discussion_r124722777
--- Diff:
metron-maven-archetypes/metron-maven-parser-extension-archetype/src/main/resources/archetype-resources/metron-parser-__parserName__-bundle/pom.xml
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/624
The final commits are intended to migrate the parser integration tests into
a driver that just executes the bolt without storm or kafka. This should save
minutes of time and set us up for new
Github user JonZeolla closed the pull request at:
https://github.com/apache/metron/pull/586
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user ottobackwards reopened a pull request:
https://github.com/apache/metron/pull/580
METRON-942 [NO MERGE UNTIL METRON-777] Rest api and configuration for
Metron parser extensions
## Contributor Comments
METRON-777 introduces metron extensions and metron parser
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/580
TRAVIS!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or
Github user ottobackwards closed the pull request at:
https://github.com/apache/metron/pull/580
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user JonZeolla closed the pull request at:
https://github.com/apache/metron/pull/586
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user JonZeolla reopened a pull request:
https://github.com/apache/metron/pull/586
METRON-508 Expand Elasticsearch templates to support the standard bro logs
## Contributor Comments
This PR makes it easier for someone with an existing bro install to send
some of their log
Github user ottobackwards commented on a diff in the pull request:
https://github.com/apache/metron/pull/624#discussion_r124811748
--- Diff:
metron-platform/metron-parsers/src/test/java/org/apache/metron/parsers/integration/ParserDriver.java
---
@@ -0,0 +1,168 @@
+/**
---
Github user dlyle65535 commented on the issue:
https://github.com/apache/metron/pull/614
+1. Used this with a largish instance, worked well, thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/620
If you want to make it specific to 'Alert' then I'm fine with that. I'm
not crazy about 'AlertsDTO', would prefer to keep the search result context in
the name, something like
57 matches
Mail list logo