metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jjmeyer0 <...@git.apache.org>
Subject [GitHub] incubator-metron issue #316: METRON-503: Metron REST API
Date Thu, 12 Jan 2017 22:26:14 GMT
Github user jjmeyer0 commented on the issue:

    https://github.com/apache/incubator-metron/pull/316
  
    @merrimanr, the reasoning I used to include the http status code in the error message
format is if there is a need to send these messages to a downstream system. For example, let's
say a developer is integrating with the Metron API. For some reason they want to drop all
error responses on a queue for processing by another system. If the status code didn't exist
in the error format some context would be lost. But to your point maybe it doesn't buy us
much. I don't have a strong preference either way on this one. However, maybe at some point
it may be worth having a custom attribute called `code` that would allow a user to look up
the errors in documentation. It could potentially show things like common causes and workarounds.
That sounds like a separate PR with a lot of discussion around it though.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message