[
https://issues.apache.org/jira/browse/METRON-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16673501#comment-16673501
]
ASF GitHub Bot commented on METRON-1850:
----------------------------------------
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/1250
I'm just not sure we *need* to shut them down. It's not like there's
writing or state-related concerns that push the need to finish with a formal
shutdown. The only time we would ever shutdown a client connection would be
when we're killing the topology, right?
I really think we need to get this client code out of the bolts. I looked a
bit through the Stellar code and if we *really* think we need this, I think it
can be accomplished through a change to the `FunctionResolver` classes. I'm
going to noodle on this a bit.
> 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)
