Ryan Merriman commented on METRON-503:


Thank you for the suggestion!  I had not really considered Knox but this is an 
interesting idea.  

Most of the services we need to write will contain fairly complex logic.  It 
won't be just simple calls to Hadoop services.  After reading your suggestion, 
I spent some time today reading the Knox documentation.  My takeaway (based on 
limited research so far) is that there is good support for proxying and 
securing requests to other REST APIs (Kerberos support is very attractive).  As 
far as actually developing and implementing these services, I did not come away 
confident about being able to quickly develop and deploy custom JAXRS REST 
services directly in Knox.  I looked primarily at the 
https://knox.apache.org/books/knox-0-9-1/dev-guide.html and could not find any 
explanation or examples around custom JAXRS REST services.  Maybe I'm just 
looking in the wrong place.  One of the primary benefits of Spring is that it 
is very well documented, easy to get up and running, and there are a ton of 
examples out there.  Am I completely off here?

Maybe we can leverage both?  A possibility I thought of is to develop and host 
our services independent of Knox and put Knox in front to handle security.  
Seems pretty standard for Knox to proxy requests to services running 
independent of Knox.

> Metron REST API
> ---------------
>                 Key: METRON-503
>                 URL: https://issues.apache.org/jira/browse/METRON-503
>             Project: Metron
>          Issue Type: New Feature
>            Reporter: Ryan Merriman
>            Assignee: Ryan Merriman
>         Attachments: Metron REST API.docx
> As discussed on the dev list ([DISCUSS] Metron REST API Requirements), this 
> Jira includes adding a REST API to Metron.

This message was sent by Atlassian JIRA

Reply via email to