[
https://issues.apache.org/jira/browse/METRON-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15848950#comment-15848950
]
ASF GitHub Bot commented on METRON-503:
---------------------------------------
Github user jjmeyer0 commented on the issue:
https://github.com/apache/incubator-metron/pull/316
@merrimanr you are right about guava. I'll remove my uses of it. Plus, Java
has a lot of those functions built in now. No reason I shouldn't use those
instead.
I agree that the guava issue should be taken care of separately. Right now,
I think we should allow a user to set an envitonment variable to point to which
guava to use (similar to hibernate and mysql). This will make it easier for us
to run it outside of our IDE.
I think your changes look pretty good. Really nice clean up/tests. We've
changed a lot, so I want to do another pass though.
I think we should still have our `HdfsService`. Right now, I think using
`FileSystem` directly works for us. Using Knox is a good idea, but it probably
needs to be optional. My thought is having the service will help us achieve
that. You are probably right though. If we can achieve everything with WebHDFS
it's better for our service to use that. This PR is already really big though.
Maybe we can have that as a take away?
> 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
(v6.3.15#6346)
