[ 
https://issues.apache.org/jira/browse/METRON-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16149537#comment-16149537
 ] 

ASF GitHub Bot commented on METRON-1146:
----------------------------------------

Github user ottobackwards commented on a diff in the pull request:

    https://github.com/apache/metron/pull/727#discussion_r136438190
  
    --- Diff: 
metron-stellar/stellar-common/src/main/java/org/apache/metron/stellar/dsl/functions/StringFunctions.java
 ---
    @@ -450,4 +454,40 @@ public Object apply(List<Object> strings) {
         }
       }
     
    +  @Stellar( name = "PARSE_JSON_STRING"
    +          , description = "Returns a JSON object for the specified JSON 
string"
    +          , params = {
    +            "str - the JSON String to convert, may be null"
    +          }
    +          , returns = "an Object containing the parsed JSON string"
    +  )
    +  public static class ParseJsonString extends BaseStellarFunction {
    +
    --- End diff --
    
    So we are just returning whatever we get back from Jackson to the caller.  
Meaning that they have to understand the content of the json in order to write 
the expression correctly.  This needs to be documented if it stays like this.
    
    I am not sure I like that.  Can you give the use cases or circumstances 
that where you imagine this being used?  What are the bounds?
    
    
    



> Add ability to parse JSON string into JSONObject for stellar
> ------------------------------------------------------------
>
>                 Key: METRON-1146
>                 URL: https://issues.apache.org/jira/browse/METRON-1146
>             Project: Metron
>          Issue Type: Bug
>            Reporter: Anand Subramanian
>            Assignee: Anand Subramanian
>
> Use jackson to parse a given JSON string and return a JSONObject on the 
> stellar. For example:
> {code}
> MAP_GET( 'bar', PARSE_JSON_STRING(  '{ "foo" : 1, "bar" : 2}' )
> {code}
> would give the output 2



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to