I also might be worth while to overload '+' in Stellar to operate on
primitive data structures like String, List or Map as well as numeric
types. Then again, that way sometimes leads to dragons.
On Mon, Apr 10, 2017 at 3:07 PM, Matt Foley wrote:
> Hi Kyle,
> For now at least, it seems to me tha
Hi Kyle,
For now at least, it seems to me that something with as much core usefulness,
and presumably non-customer-specific, as string concat should go into
metron-common. That said, I suspect Mike is right that JOIN would be
sufficient. But if that fits your use case poorly, just say so.
--M
I am working on that. What i’m shooting for is having archetypes for
parsers, stellar function libraries, and - metron extensions.
The stellar work will be a follow on however.
On April 10, 2017 at 13:13:46, Michael Miklavcic (
michael.miklav...@gmail.com) wrote:
Hey Kyle,
It probably b
Hey Kyle,
It probably belongs here -
https://github.com/apache/incubator-metron/blob/master/metron-platform/metron-common/src/main/java/org/apache/metron/common/dsl/functions/StringFunctions.java
There is an existing JOIN function for strings - might this suit your
needs? I didn't see a unit test
I have the need for a new Stellar function to perform string concatenation.
I have it implemented but am curious about where new functions should live
given the new capabilities around 3rd party Stellar function libraries.
So, I guess my question is, should this function live in:
1) metron-common