Github user asfgit closed the pull request at:
https://github.com/apache/metron/pull/611
---
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 mattf-horton commented on the issue:
https://github.com/apache/metron/pull/611
Thanks, @JonZeolla .
---
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
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/579
I just kicked up https://github.com/apache/metron/pull/612, which
theoretically fixes the unit tests (and simplifies them a lot). Straight
replacing the logs would work, but we might want
GitHub user justinleet opened a pull request:
https://github.com/apache/metron/pull/612
METRON-962: Configuration Based Unit Tests and Add integration tests
## Contributor Comments
Admittedly, this mixes a couple things together. I originally intended to
get rid of JUnit3
Github user JonZeolla commented on the issue:
https://github.com/apache/metron/pull/611
+1 by inspection
---
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,
Github user mattf-horton commented on a diff in the pull request:
https://github.com/apache/metron/pull/606#discussion_r119960003
--- Diff:
metron-platform/metron-common/src/main/java/org/apache/metron/common/stellar/StellarCompiler.java
---
@@ -76,14 +92,80 @@ public
Github user mattf-horton commented on a diff in the pull request:
https://github.com/apache/metron/pull/606#discussion_r119928459
--- Diff:
metron-analytics/metron-profiler-client/src/main/java/org/apache/metron/profiler/client/window/WindowProcessor.java
---
@@ -89,7 +89,7 @@
Github user mattf-horton commented on a diff in the pull request:
https://github.com/apache/metron/pull/606#discussion_r119928654
--- Diff:
metron-platform/metron-common/src/main/antlr4/org/apache/metron/common/stellar/generated/Stellar.g4
---
@@ -139,9 +139,21 @@
Github user mattf-horton commented on a diff in the pull request:
https://github.com/apache/metron/pull/606#discussion_r119931000
--- Diff:
metron-platform/metron-common/src/main/java/org/apache/metron/common/stellar/StellarCompiler.java
---
@@ -40,14 +40,22 @@
import static
Github user mattf-horton commented on a diff in the pull request:
https://github.com/apache/metron/pull/606#discussion_r119948393
--- Diff:
metron-platform/metron-common/src/main/java/org/apache/metron/common/stellar/StellarCompiler.java
---
@@ -40,14 +40,22 @@
import static
GitHub user mattf-horton opened a pull request:
https://github.com/apache/metron/pull/611
METRON-979 markdown errors in site-book, part 3
## Contributor Comments
Due to an integration error on my part, one editorial glitch remains, in
the form of an unresolved merge fragment in
Github user mattf-horton commented on the pull request:
https://github.com/apache/metron/commit/d5abcf429dad3c284a5f2469c0fb99713844be02#commitcomment-22423694
In metron-deployment/Kerberos-manual-setup.md:
In metron-deployment/Kerberos-manual-setup.md on line 388:
That's a
GitHub user mattf-horton opened a pull request:
https://github.com/apache/metron/pull/610
METRON-877 Extract core implementation and UDF support, create
metron-stellar module
## Contributor Comments
The design document has been available for some time at
Github user JonZeolla commented on the pull request:
https://github.com/apache/metron/commit/d5abcf429dad3c284a5f2469c0fb99713844be02#commitcomment-22423223
In metron-deployment/Kerberos-manual-setup.md:
In metron-deployment/Kerberos-manual-setup.md on line 388:
I don't think
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/530
@simonellistonball I have been tracking master and porting changes over as
part of the merge ( as required since the parsers have moved). PR's that are
in the queue after this hits ( if it
GitHub user cestella opened a pull request:
https://github.com/apache/metron/pull/609
METRON-987: Allow stellar enrichments to be specified by a list as well as
a map
## Contributor Comments
Currently, stellar enrichments are specified by a map associating fields
with the
Github user simonellistonball commented on the issue:
https://github.com/apache/metron/pull/530
@ottobackwards there have been a number of tweaks to the parsers since this
first went in, do you anticipate any need to port any of those by hand, or will
this structure pick up changes
Btw. I expounded on this reply in the issue, but no mail is sent out for edits,
so please refer to the pr.
On June 6, 2017 at 17:05:57, ottobackwards (g...@git.apache.org) wrote:
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/530
@nickwallen I
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/530
@nickwallen I mis-understood your question about what you should be able to
do, yes you should be able to build the nick parser, and put it in parser
extensions and add in all the things nec.
Github user kylerichardson commented on the issue:
https://github.com/apache/metron/pull/579
Given these unit tests have been broken for quite some time and @ctramnitz
has thoroughly tested in his environment and that this is a relatively minor
change, I'm okay to move it forward
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/530
that is what METRON-942 is. https://github.com/apache/metron/pull/580.
This is the part that is left out of this PR, to trim the scope down.
942 is 777 + REST API to install
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/530
Shouldn't I be able to build the new parser bundles and then deploy them
somehow? Even if it is laborious to do with this PR, that would be the test.
There has to be something net new that can
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/530
Since this PR is not adding new **functionality** the testing is the usual
smoke test for parser functionality per functional area ( Full Dev has data,
Metron UI sees the configurations ).
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/530
The answer is 1. I did not submit until this set of functionality was done
because it is completely end to end testable. A smaller part that is not
working or demonstrable did not seem
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/530
Can you outline a set of specific steps for testing this PR?
---
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/530
@ottobackwards What is your goal for this PR?
1. Do you want this merged as-is into master after review?
2. Or did you submit this to get buy-in as a proof-of-concept, that we can
then
Github user mattf-horton commented on the issue:
https://github.com/apache/metron/pull/600
+1 by inspection. Thanks for expanding the unit test to be more complete
and understandable.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/600
@mattf-horton Updated with a more explicit set of unit tests around it and
a comment explaining the assumption made by the function. Let me know if
there's anything else you want or need to make
Hope you don’t mind if I chime in. There are a couple very basic points which
are in the documentation, but may not jump out at a new user, who is trying to
learn Metron at the same time as MaaS.
1. In the thread below there is only a brief reference to the main
documentation page for MaaS,
Github user justinleet commented on a diff in the pull request:
https://github.com/apache/metron/pull/600#discussion_r120434003
--- Diff:
metron-platform/metron-common/src/main/java/org/apache/metron/common/utils/KafkaUtils.java
---
@@ -68,12 +68,14 @@
return ret;
So, first off, it's not a basic question at all and thanks for asking it.
I'm sure if it's not clear to you, then it's not clear to many and bears
some reinforcement and clarification.
- Metron does indeed enable the deployment and use of machine learning
models on data ingested into
Github user mattf-horton commented on a diff in the pull request:
https://github.com/apache/metron/pull/600#discussion_r120429871
--- Diff:
metron-platform/metron-common/src/main/java/org/apache/metron/common/utils/KafkaUtils.java
---
@@ -68,12 +68,14 @@
return ret;
Dear Mr Stella,
I didn't know who you are since today when I read more about you.
So first, thanks for your time answering to my previous post.
Here below, there are some other questions, because I read the available
guidelines about Metron focusing on Maas but for me it is not clear how to
Thanks!
On June 6, 2017 at 11:06:25, Anand Subramanian (asubraman...@hortonworks.com)
wrote:
Hey Otto,
On Ambari UI -> Metron -> Config -> Advanced -> Advanced metron-env, can you
set the following, then restart Metron REST and Management UI?
Metron JDBC Driver = org.h2.Driver
Metron
Hey Otto,
On Ambari UI -> Metron -> Config -> Advanced -> Advanced metron-env, can you
set the following, then restart Metron REST and Management UI?
Metron JDBC Driver = org.h2.Driver
Metron JDBC password = root
Metron JDBC platform = h2
Metron JDBC URL = jdbc:h2:file:~/metrondb
Metron JDBC
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/530
https://github.com/apache/metron/pull/580/commits/eefdd4f0368e09b4d1b7050a880328fb299acb62
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/530
So I need to update the archetype readme and replace the todo for install
with the pr instructions ( again in METRON-942 )
---
If your project is set up for it, you can reply to this email
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/530
So - this PR is the system re-architecture part - enabling end user stuff.
METRON-942 is the end user facing stuff ( including installing your parser
through rest ).
Github user justinleet commented on a diff in the pull request:
https://github.com/apache/metron/pull/600#discussion_r120369355
--- Diff:
metron-platform/metron-common/src/main/java/org/apache/metron/common/utils/KafkaUtils.java
---
@@ -68,12 +68,14 @@
return ret;
Github user justinleet commented on a diff in the pull request:
https://github.com/apache/metron/pull/607#discussion_r120367143
--- Diff:
metron-interface/metron-rest/src/main/java/org/apache/metron/rest/service/impl/StormStatusServiceImpl.java
---
@@ -49,6 +44,11 @@ public
Github user nickwallen commented on the issue:
https://github.com/apache/metron/pull/530
@ottobackwards Where are the "User Guide"-type docs? I want to start using
your extension system as a user would and then work into the implementation
from there.
---
If your project is set
Github user ctramnitz commented on the issue:
https://github.com/apache/metron/pull/579
I'm running this myself and actively parsing PaloAlto logs with this change
for about 3 weeks. You can also see that the changes are fairly trivial and
that structure and naming follows the
42 matches
Mail list logo
