[
https://issues.apache.org/jira/browse/METRON-987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043259#comment-16043259
]
ASF GitHub Bot commented on METRON-987:
---------------------------------------
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/609
@justinleet yes, agreed. I wanted to get this functionality in and have it
be backwards compatible for the short term, but ultimately, I think that it's a
better approach and we should work toward phasing out the map-based approach.
The issue is that there are a few other places that also need to be normalized:
* the field transformations
* the importer config
* possibly others that I am not thinking about
Anyway, to answer your question, yes I'll probably start a discuss thread
on that tomorrow and construct some JIRAs to see if
* other people think deprecation is a good thing to work towards
* how in the heck we should accomplish it
> Allow stellar enrichments to be specified by a list as well as a map
> --------------------------------------------------------------------
>
> Key: METRON-987
> URL: https://issues.apache.org/jira/browse/METRON-987
> Project: Metron
> Issue Type: Improvement
> Reporter: Casey Stella
> Assignee: Casey Stella
>
> Currently, stellar enrichments are specified by a map associating fields with
> the stellar expressions associated with the fields. There is a significant
> downside here in that you cannot update previously assigned fields. For
> instance, the following cannot be represented currently:
> {code}
> "fieldMap": {
> ...
> "stellar" : {
> "config" : {
> "hostname" : "if ENDS_WITH(hostname, '.') then CHOP(hostname) else
> hostname",
> "hostname" : "TO_LOWER(hostname)"
> }
> }
> }
> {code}
> A consequent of this deficiency is that we also cannot use temporary
> variables and unset them after their use inside an enrichment group.
> The proposed change is to allow users to use lists of strings representing
> stellar expression assignments with the same syntax as the Stellar REPL.
> This would be as an alternative to maps, but the map syntax would also be
> supported for legacy.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
