[
https://issues.apache.org/jira/browse/METRON-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16484054#comment-16484054
]
ASF GitHub Bot commented on METRON-1568:
----------------------------------------
Github user ottobackwards commented on a diff in the pull request:
https://github.com/apache/metron/pull/1021#discussion_r189924019
--- Diff:
metron-platform/metron-common/src/main/java/org/apache/metron/common/configuration/enrichment/handler/StellarConfig.java
---
@@ -142,8 +143,14 @@ else if(kv.getValue() instanceof List) {
{
--- End diff --
I'm trying to wrap my head around why you need the special handling in the
variable resolver.
If one of the vars points to a map, that is it. You don't need to do any
special dance.
You can have the variable context 'builder' ( config whatever ) allow
naming the message as a var with a certain name and that is it.
I don't understand why all the extra stuff is required. IE. why the
variable resolver needs to know it is a map. It is just a var.
> Stellar should have a _ special variable which returns the message in map form
> ------------------------------------------------------------------------------
>
> Key: METRON-1568
> URL: https://issues.apache.org/jira/browse/METRON-1568
> Project: Metron
> Issue Type: Improvement
> Reporter: Casey Stella
> Priority: Major
>
> In order to support functions which operate on the whole message, we should
> have a special variable (_, keeping with the vaguely scala theme) which can
> return the entire underlying message. This map should be immutable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
