metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cestella <>
Subject [GitHub] incubator-metron issue #142: METRON-204: Field Transformation Domain Specifi...
Date Mon, 13 Jun 2016 13:49:19 GMT
Github user cestella commented on the issue:
    So, I think the main disadvantage of using groovy or any of the scripting
    engine integrations is speed and expressibility.  Having a targeted domain
    specific language is going to be a lot simpler to parse than something more
    complex like groovy (or javascript for that matter).  It's hardly even a
    DSL, frankly, just the ability to compose functions, which seems like a
    sweet spot between the expressivity and complexity.  If we want to
    implement a FieldTransformation which is a scripting language, there's
    nothing keeping us from doing this.  The other reason I like a simple DSL
    with just function composition is that I'd *really* prefer to not give
    users enough rope to hang themselves with here if we can help it.  This DSL
    really exposes only the things you can do in one line of code.  If it's
    more than one line of code, we should be considering that a feature in the
    If we really want to integrate a scripting engine in the future, we can
    create a separate FieldTransformer to do it in just one class.
    On Mon, Jun 13, 2016 at 9:38 AM, Nick Allen <>
    > Love the functionality that you are creating with this. I am curious if it
    > would make more sense to provide this functionality via an existing
    > JVM-capable language like Groovy, etc, rather than inventing our own DSL.
    > At first glance, it seems there are a lot of advantages in doing it this
    > way. What were the pros/cons when you thought through this?
    > —
    > You are receiving this because you authored the thread.
    > Reply to this email directly, view it on GitHub
    > <>,
    > or mute the thread
    > <>
    > .

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 enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message