Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/599
@merrimanr Conflicts resolved
---
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 w
Github user merrimanr commented on a diff in the pull request:
https://github.com/apache/metron/pull/620#discussion_r127832531
--- Diff: metron-interface/metron-alerts/src/app/service/data-source.ts ---
@@ -0,0 +1,62 @@
+/**
+ * Licensed to the Apache Software Foundation (AS
Github user asfgit closed the pull request at:
https://github.com/apache/metron/pull/647
---
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 enab
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/647
+1 validated with instructions in the PR description. Nice work!
---
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 doe
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/599
@mmiklavc looks like there are some merge conflicts. If you don't mind
resolving those I will get this reviewed.
---
If your project is set up for it, you can reply to this email and have your
re
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/599
I would love to get this in
---
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 wis
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/645
Their status will "Active" but you'll see Kerberos errors in the Storm UI.
---
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 pr
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/645
Ok. So they will "look like" they are running, but they are not actually
consuming data. I just wanted to be sure.
I will run this through a test so we can get this.
---
If your projec
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/645
Without it, the enrichment and indexing topologies don't work on a
Kerberized environment because the Storm worker childopts property needs the
"-Djava.security.auth.login.config=/path/to/client_ja
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/645
What happens without this PR? What behavior are we correcting?
---
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 nickwallen commented on the issue:
https://github.com/apache/metron/pull/647
@merrimanr Ran it through a full test as described in the PR description
and its looking good. Please take a look when you can.
---
If your project is set up for it, you can reply to this email
Github user DomenicPuzio commented on the issue:
https://github.com/apache/metron/pull/359
Yep, we can wrap it up! Thanks, all!
---
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
en
Github user DomenicPuzio closed the pull request at:
https://github.com/apache/metron/pull/359
---
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 i
Github user merrimanr commented on the issue:
https://github.com/apache/metron/pull/359
@DomenicPuzio, this has been resolved by
https://github.com/apache/metron/pull/603. Can we close this PR?
---
If your project is set up for it, you can reply to this email and have your
reply app
The plan around the mpack with regards to elastic search and solr support
and options is extremely important and as of yet undecided.
On July 17, 2017 at 03:00:42, Simon Elliston Ball (
si...@simonellistonball.com) wrote:
> I assume you're taking about METRON-939. The upgrade is not a huge chang
I assume you're taking about METRON-939. The upgrade is not a huge change, and
unlikely to touch any of the bulk writing pieces. The main thing outstanding on
the PR is log4j dependency conflicts from the new ES client.
There's no work in that PR to do anything around mpack based install either
16 matches
Mail list logo
