Github user cestella commented on the issue:
https://github.com/apache/incubator-metron/pull/395
I also wanted to mention one of the reasons I am particularly sensitive to
having multiple components that do *very nearly* the same thing. I made this
mistake early on in the project (and will probably make it again, because..you
know, I don't learn ;).
Stellar started as a predicate language only for threat triage rules. As
such, when the task of creating Field Transformations came to me, I needed
something like Stellar except I needed it to return arbitrary objects, rather
than just booleans. In my infinite wisdom, I chose to fork the language,
create a second, more specific DSL for field transformations, thereby creating
"Metron Query Language" and "Metron Transformation Language."
I felt a nagging feeling at the time that I should just expand the query
language, but I convinced myself that it would require too much testing and it
would be a change that was too broad in scope. It took 3 months for me to get
around to unifying those languages and if we had more people using it, it would
have been an absolute nightmare. This may be a "once bitten, twice shy" thing,
but I think it's a good policy in general. Pardon the interlude; just wanted
to give some context.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
