Github user asfgit closed the pull request at:
https://github.com/apache/incubator-metron/pull/465
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-metron/pull/464
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-metron/pull/466
---
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
Github user cestella commented on the issue:
https://github.com/apache/incubator-metron/pull/438
Ok, I'm +1 on this pending successful 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
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-metron/pull/463
---
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
That's what this fix was for:
https://github.com/apache/incubator-metron/pull/422. I realize it is
getting deprecated, but would have preferred to have something actually
working before we deprecate. But alas...
On Sat, Feb 25, 2017 at 10:42 AM, David Lyle wrote:
> I'm
Sounds like we're in agreement. I did a quick dry run and agree with Nick,
easy fix. I'm ready to push but want to be sure everyone's good with the
history. Here's what it will look like:
commit 8b4fa79d19be992ad270df7d1780db7f4b8ce176
Author: kylerichardson
Date:
Nick, what are your thoughts on adjusting the script to error out or prompt
for an email address if one can't be found?
On Mon, Feb 27, 2017 at 8:51 PM, Nick Allen wrote:
> I think revert and commit again is the best way to go. Not a big deal.
>
> On Mon, Feb 27, 2017 at
Github user kylerichardson commented on the issue:
https://github.com/apache/incubator-metron/pull/467
+1 passes unit and integration tests, ran through @cestella's test script
successfully
Thanks for your patience and for fixing!
---
If your project is set up for it, you
+1
On Feb 27, 2017 10:12 PM, "Casey Stella" wrote:
> +1
>
> On Mon, Feb 27, 2017 at 10:11 PM, Kyle Richardson <
> kylerichards...@gmail.com
> > wrote:
>
> > Just to confirm. Please reply +1 if you're okay for me to commit the
> revert
> > / re-commit of METRON-646 (PR#441).
This is in travis though
On February 27, 2017 at 21:49:57, Ryan Merriman (merrim...@gmail.com) wrote:
nodemanager.LocalDirsHandlerService
(LocalDirsHandlerService.java:updateDirsAfterTest(356)) - Most of the
disks failed. 1/1 local-dirs are bad:
I think revert and commit again is the best way to go. Not a big deal.
On Mon, Feb 27, 2017 at 6:55 PM, Casey Stella wrote:
> I think it should be changed, but I'm not sure how to change it. I think it
> should be changed because our git history is our legal trail of
>
Sure. It could validate the email address before letting you proceed.
It tries to get the email from the author's Github profile. If the author
doesn't make one public, it will come back as 'null' and prompt you to
change it. Of course, it will just use 'null' if you don't provide an
Just to confirm. Please reply +1 if you're okay for me to commit the revert
/ re-commit of METRON-646 (PR#441).
Thanks,
Kyle
On Mon, Feb 27, 2017 at 9:25 PM, Casey Stella wrote:
> Yeah, I'd think there does not exist a time in which the email should be
> null. I'd rather
Nothing from me, sorry!
On Mon, Feb 27, 2017 at 9:31 PM, Otto Fowler
wrote:
> I took out the parallel processing and now I see the error:
>
> ---
>
> T E S T S
>
>
I took out the parallel processing and now I see the error:
---
T E S T S
---
Running org.apache.metron.maas.service.MaasIntegrationTest
2017-02-28 00:15:17,056 ERROR [main]
I run into this error every now and then. If I free up space on my hard drive
it goes away.
> On Feb 27, 2017, at 8:31 PM, Otto Fowler wrote:
>
> I took out the parallel processing and now I see the error:
>
> ---
>
+1
On Mon, Feb 27, 2017 at 10:11 PM, Kyle Richardson wrote:
> Just to confirm. Please reply +1 if you're okay for me to commit the revert
> / re-commit of METRON-646 (PR#441).
>
> Thanks,
> Kyle
>
> On Mon, Feb 27, 2017 at 9:25 PM, Casey Stella
GitHub user cestella opened a pull request:
https://github.com/apache/incubator-metron/pull/468
METRON-744: Allow Stellar functions to be loaded from HDFS
## Description
The benefit of Stellar is that adding new functionality is as simple as
providing a Jar. This enables people
Sure,
I am not doing the ansible work for any other reason than ansible is what
we have now, and what works.
I realized that deployment of the current parsers needs to work with ambari
etc, and it is next. I just did ansible first, because that is what works
for quick-dev etc.
As far as how to
Github user ottobackwards commented on a diff in the pull request:
https://github.com/apache/incubator-metron/pull/436#discussion_r103235131
--- Diff: metron-deployment/roles/kibana/README.md ---
@@ -1,35 +0,0 @@
-Kibana 4
--- End diff --
Is this documented
Github user ottobackwards commented on a diff in the pull request:
https://github.com/apache/incubator-metron/pull/436#discussion_r103238671
--- Diff: metron-deployment/roles/kibana/README.md ---
@@ -1,35 +0,0 @@
-Kibana 4
--- End diff --
The file I commented was
Hi Otto,
It will have a pretty major effect. We agreed a bit back that we wanted, as
a community, to reduce reliance on Ansible, so I think an Ansible-based
parser loader would be sub-optimal. You may be working on this a bit in
early. There are some some major changes on the way that will could
Github user ottobackwards commented on a diff in the pull request:
https://github.com/apache/incubator-metron/pull/436#discussion_r103239678
--- Diff: metron-deployment/roles/java_jdk/defaults/main.yml ---
@@ -15,4 +15,4 @@
# limitations under the License.
#
---
Not sure how https://github.com/apache/incubator-metron/pull/436 is going
to effect this, but it will.
On February 26, 2017 at 23:04:32, Otto Fowler (ottobackwa...@gmail.com)
wrote:
OK, Current status
Complete:
* Parsers broken out into common, base ( raw types - csv, json, grok ) and
Github user dlyle65535 commented on a diff in the pull request:
https://github.com/apache/incubator-metron/pull/436#discussion_r103235875
--- Diff: metron-deployment/roles/kibana/README.md ---
@@ -1,35 +0,0 @@
-Kibana 4
--- End diff --
Is what documented? I just
Github user dlyle65535 commented on a diff in the pull request:
https://github.com/apache/incubator-metron/pull/436#discussion_r103240842
--- Diff: metron-deployment/roles/kibana/README.md ---
@@ -1,35 +0,0 @@
-Kibana 4
--- End diff --
Ah, it is, but not well. I'll
Github user cestella commented on the issue:
https://github.com/apache/incubator-metron/pull/467
Ok, I ran this up and tested it and I got the results I expect, but I'd
like some independent confirmation by @kylerichardson
---
If your project is set up for it, you can reply to this
Metron-common is shaded so that we can use a more recent version of guava
which some of our functionality relies upon but does not play nice with the
version brought in with HBase (by relocating gauva). I, personally,
believe that we should
- Reduce our dependence on guava until we no longer
Github user jjmeyer0 commented on the issue:
https://github.com/apache/incubator-metron/pull/316
@merrimanr Good catch on this. I'll take a look again, but I think it's
looking good!
---
If your project is set up for it, you can reply to this email and have your
reply appear on
The release passes:
+1 (binding):
- James Sirota
- David Lyle
- Ryan Merriman
- Casey Stella
+1 (non-binding):
- Justin Leet
metron-api-0.3.1.jar, metron-common-0.3.1.jar,
htrace-core-3.1.0-incubating.jar define 756 overlapping classes:
[WARNING] -
org.apache.htrace.fasterxml.jackson.databind.introspect.BasicBeanDescription
[WARNING] -
org.apache.htrace.fasterxml.jackson.databind.KeyDeserializer$None
[WARNING]
Is there a reason why we shade ALL of the jars? For example -
metron-common is shaded. But it is never ‘deployed’ to storm or yarn or mr
as a stand alone…
I would think that only the ‘outward’ facing libs would be shaded.
Couple thoughts:
1. I see the Accumulo class loader allows multiple clients with potentially
conflicting loads, via the “context” mechanism. That’s good. NiFi also used a
multi-classloader mechanism to support potentially conflicting side-loads of
their Processor bundles (“nars”), but I don’t
Github user merrimanr commented on the issue:
https://github.com/apache/incubator-metron/pull/316
Finally figured this one out. I wasn't able to reproduce the issue because
my maven version was a couple minor releases behind (on 3.3.9 now for what it's
worth). Once I got past that
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-metron/pull/441
---
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
Github user merrimanr commented on the issue:
https://github.com/apache/incubator-metron/pull/441
+1 from me
---
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 dlyle65535 commented on a diff in the pull request:
https://github.com/apache/incubator-metron/pull/436#discussion_r103241052
--- Diff: metron-deployment/roles/java_jdk/defaults/main.yml ---
@@ -15,4 +15,4 @@
# limitations under the License.
#
---
Hi All,
The benefit of Stellar is that adding new functionality is as simple as
providing a Jar. This enables people who want to integrate with Metron to
easy add enrichments or other functionality. The snag currently with this
is that we provide a single jar, so all stellar functions that we
After some discussion with David, I am going to rebase my work off of
PR-436 ( ansible deploys with mpack )
On February 27, 2017 at 10:31:26, Otto Fowler (ottobackwa...@gmail.com)
wrote:
Sure,
I am not doing the ansible work for any other reason than ansible is what
we have now, and what
Github user nickwallen commented on the issue:
https://github.com/apache/incubator-metron/pull/449
I made the required changes and updated the PR description to reflect that.
Please take a look and review.
---
If your project is set up for it, you can reply to this email and have
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-metron/pull/438
---
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
Ok, so here's the story... Ryan was nice enough to commit my recent PR and
for whatever reason my github username but not my email address appears in
the commit author (see below).
commit 41fc0ddc9881d9cfdd8bae129c0bb7800a116d4c
Author: kylerichardson
Date: Mon Feb 27 11:38:55 2017 -0600
I think it should be changed, but I'm not sure how to change it. I think it
should be changed because our git history is our legal trail of
attribution. Mucking with it is relatively serious business.
As to how, normally I'd say git commit --amend --author "kylerichardson <
44 matches
Mail list logo