You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "Casey Stella (JIRA)" <ji...@apache.org> on 2017/09/13 23:50:01 UTC
[jira] [Assigned] (METRON-1135) Make Stellar field transformations
handle nulls properly
[ https://issues.apache.org/jira/browse/METRON-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Casey Stella reassigned METRON-1135:
------------------------------------
Assignee: Casey Stella
> Make Stellar field transformations handle nulls properly
> --------------------------------------------------------
>
> Key: METRON-1135
> URL: https://issues.apache.org/jira/browse/METRON-1135
> Project: Metron
> Issue Type: Bug
> Reporter: Casey Stella
> Assignee: Casey Stella
>
> As it stands, stellar field transformations disallow users to set variables to null (and thus remove the field). This should be corrected. For instance,
> {code}
> "fieldTransformations" : [
> { "transformation" : "STELLAR"
> ,"output" : [ "new_field", "new_field2"]
> ,"config" : {
> "new_field" : "old_field"
> ,"new_field2" : "old_field2"
> ,"old_field" : "null"
> ,"old_field2" : "null"
> }
> }
> ]
> {code}
> should rename "old_field" to "new_field and "old_field2" to "old_field2" The current behavior is to keep all 4 fields and to not change old_field or old_field2 at all.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)