You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/11/01 21:15:00 UTC

[jira] [Commented] (METRON-1850) Stellar REST function

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

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

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

    https://github.com/apache/metron/pull/1250#discussion_r230200490
  
    --- Diff: metron-platform/metron-common/src/main/java/org/apache/metron/common/bolt/ConfiguredParserBolt.java ---
    @@ -36,4 +44,20 @@ protected SensorParserConfig getSensorParserConfig(String sensorType) {
         return getConfigurations().getSensorParserConfig(sensorType);
       }
     
    +  @Override
    +  public void prepare(Map stormConf, TopologyContext context, OutputCollector collector) {
    --- End diff --
    
    Same as the comment for enrichment - do we want this tied to the bolts this way?


> Stellar REST function
> ---------------------
>
>                 Key: METRON-1850
>                 URL: https://issues.apache.org/jira/browse/METRON-1850
>             Project: Metron
>          Issue Type: New Feature
>            Reporter: Ryan Merriman
>            Priority: Major
>
> It would be useful to be able to enrich messages with Stellar using 3rd party (or internal) REST services.  At a minimum this function would:
>  * Stellar function available to GET from an HTTP API
>  * Optional parameters for basic auth (user/password) which generate correct Authorization header
>  * Function returns null value for errors, connection failures etc and logs error
>  * Function must provide and use pooled connection objects at the process level
>  * Function must send Accept: application/json header
>  * A global setting must be available to set a proxy for all API calls, and if present the proxy must be used.
>  * Proxy authentication must also be supported using basic auth.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)