[
https://issues.apache.org/jira/browse/METRON-1568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16483944#comment-16483944
]
ASF GitHub Bot commented on METRON-1568:
----------------------------------------
Github user cestella commented on a diff in the pull request:
https://github.com/apache/metron/pull/1021#discussion_r189900746
--- 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 --
Well, I added it because I came across it multiple times in data science
use-cases. Specifically, the way that we do model application via MaaS (and
other model applications) presumes that the user will filter just the fields
into the model, rather than having the model select it. This puts an undue
burden on the user as the model knows which fields it wants and the user may
not, so being able to pass the whole message lets the model do the decision. I
think that `_` is a natural way to do that. To be fair, also, this is a
capability inherent to the VariableResolver, not the grammar itself, which I
thought was reasonable. SOme variable resolvers won't support it and some will.
Thoughts?
> 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)
