GitHub user merrimanr opened a pull request:
https://github.com/apache/metron/pull/679
METRON-1075: Add faceted search capabilities
## Contributor Comments
This PR adds faceted search to indexing DAO. This can be tested in full
dev with Swagger. When searching with the
Good eye, Otto!
From: Otto Fowler
Date: Wednesday, August 2, 2017 at 2:12 PM
To: Matt Foley , "dev@metron.apache.org"
, "u...@metron.apache.org"
Subject: Re: profiler Syntax error
Can you try the
Agreed on Postgres. It's a lot easier to work with license-wise in apache
projects, and has a lot of the capability we need here, especially if we can
find a sensible ORM. Anyone got any thoughts on what would work there?
Simon
> On 2 Aug 2017, at 21:21, Matt Foley wrote:
>
Spring supports a variety of databases including Postgres. I have no
problem with using Postgres instead of MySQL.
On Wed, Aug 2, 2017 at 3:32 PM, Simon Elliston Ball <
si...@simonellistonball.com> wrote:
> Agreed on Postgres. It's a lot easier to work with license-wise in apache
> projects,
Hi Dima,
Is it possible that the input parser is giving an unreasonable value for
“destination_ip”? Or perhaps fails to provide an end quote for that value?
Does this profile fail on the first message to be consumed, or does it get a
ways into the data stream and then choke? In either case,
Matt,
Thank you for the suggestions. I forgot to include Zookeeper. Are there
any tradeoffs we should be aware of if we decide to use Zookeeper? Are
there guidelines for how much data can be stored in Zookeeper?
To answer your questions:
1. I think both use cases make sense so a combination
[Stellar]>>> in:= 'foo'
[Stellar]>>> TO_UPPER(in)
[!] Unable to parse: TO_UPPER(in) due to:
org.apache.metron.stellar.dsl.ParseException: Syntax error @ 1:9 no
viable alternative at input 'TO_UPPER(in'
org.apache.metron.stellar.dsl.ParseException: Unable to parse:
TO_UPPER(in) due to:
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/666
Testing Instructions beyond the normal smoke test (i.e. letting data
flow through to the indices and checking them).
# Preliminaries
Set an environment variable to indicate
GitHub user merrimanr opened a pull request:
https://github.com/apache/metron/pull/677
METRON-1073: Add option to limit fields returned from search query
## Contributor Comments
This PR adds the option to explicitly declare which fields should be
returned in search results.
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/650#discussion_r130883151
--- Diff:
metron-stellar/stellar-common/src/main/java/org/apache/metron/stellar/common/utils/math/MathOperations.java
---
@@ -0,0 +1,66 @@
+/*
+ *
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/650#discussion_r130883191
--- Diff:
metron-stellar/stellar-common/src/main/java/org/apache/metron/stellar/common/utils/math/MathOperations.java
---
@@ -0,0 +1,66 @@
+/*
+ *
Github user jjmeyer0 commented on a diff in the pull request:
https://github.com/apache/metron/pull/650#discussion_r130885709
--- Diff: metron-stellar/stellar-common/README.md ---
@@ -101,58 +101,69 @@ In the core language functions, we support basic
functional programming
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/676
+1, built with full commit build options, ran full dev, saw data.
Honestly, these errors are not what flood my logs, but it is good to chip
away
---
If your project is set up for it, you
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/650#discussion_r130880007
--- Diff: metron-stellar/stellar-common/README.md ---
@@ -581,6 +634,24 @@ In the core language functions, we support basic
functional programming primitiv
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/650#discussion_r130880080
--- Diff: metron-stellar/stellar-common/README.md ---
@@ -613,6 +684,12 @@ In the core language functions, we support basic
functional programming primitiv
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/650#discussion_r130883104
--- Diff:
metron-stellar/stellar-common/src/main/java/org/apache/metron/stellar/common/utils/math/StellarMathFunction.java
---
@@ -0,0 +1,64 @@
+/*
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/650#discussion_r130880027
--- Diff: metron-stellar/stellar-common/README.md ---
@@ -581,6 +634,24 @@ In the core language functions, we support basic
functional programming primitiv
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/650#discussion_r130879867
--- Diff:
metron-stellar/stellar-common/src/main/java/org/apache/metron/stellar/dsl/functions/MathFunctions.java
---
@@ -19,45 +19,179 @@
*/
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/650#discussion_r130879927
--- Diff: metron-stellar/stellar-common/README.md ---
@@ -110,6 +110,8 @@ In the core language functions, we support basic
functional programming primitiv
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/650#discussion_r130879898
--- Diff: metron-stellar/stellar-common/README.md ---
@@ -110,6 +110,8 @@ In the core language functions, we support basic
functional programming primitiv
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/650
Ok, I reacted to @mattf-horton and @justinleet 's comments:
* adjusted some naming and made the documentation match up
* adjusted the `ROUND` documentation to indicate half-up rounding.
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/650#discussion_r130886124
--- Diff: metron-stellar/stellar-common/README.md ---
@@ -101,58 +101,69 @@ In the core language functions, we support basic
functional programming
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/530
I'm back to looking through this again. A couple questions:
1) I was under the impression that our local copy of the nar functionality
would be a hard fork that would naturally deviate from the
Github user mattf-horton commented on the issue:
https://github.com/apache/metron/pull/650
+1, lgtm. By the way, my mentions of BiFunction were incorrect because
MathFunction takes an array of numbers as its (sole) argument. But glad to see
you added Min Args as well as Max Args.
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/530
@mmiklavc
1. I don't think we want to, or have to track it as upstream. But we do
want to keep track of bug fixes and improvements to areas where we have not
deviated. That is my
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/530
Oh profiler integration test
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/metron/pull/676
---
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 mmiklavc commented on the issue:
https://github.com/apache/metron/pull/676
Agreed @ottobackwards - we still have quite a bit of work around the
warnings related to shading and relocating jars. Thanks for the review!
---
If your project is set up for it, you can reply to
28 matches
Mail list logo