You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Ajay Yadava (JIRA)" <ji...@apache.org> on 2015/09/11 21:13:46 UTC
[jira] [Comment Edited] (FALCON-1440) Better json for triage api
[ https://issues.apache.org/jira/browse/FALCON-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14741400#comment-14741400 ]
Ajay Yadava edited comment on FALCON-1440 at 9/11/15 7:13 PM:
--------------------------------------------------------------
Hi [~raghavgautam]
Current format is in accordance with dot notation to make it easy for users to visualise the information through some tool.
Giving a JSON will not be useful in this case as users will not be able to see the relationship between various entities. DOT notation expects vertices to be in a string, also the same POJO is being used for all dot notations(entity lineage/ triage etc.) and it's not possible to stick to one particular JSON format (e.g. vertex is just a string in entity lineage), hence the reason to stick to a string instead of a JSON. This behaviour is documented for entity lineage but not for the triage api, I will fix the docs to reflect the same. Hope it clarifies.
was (Author: ajayyadava):
Hi [~raghavgautam]
Current format is in accordance with dot notation to make it easy for users to visualise the information through some tool.
Giving a JSON will not be useful in this case as users will not be able to see the relationship between various entities. Also the same POJO is being used for all dot notations(entity lineage/ triage etc.) and hence the reason to stick to a string instead of a JSON. This behaviour is documented for entity lineage but not for the triage api, I will fix the docs to reflect the same. Hope it clarifies.
> Better json for triage api
> --------------------------
>
> Key: FALCON-1440
> URL: https://issues.apache.org/jira/browse/FALCON-1440
> Project: Falcon
> Issue Type: Bug
> Reporter: Raghav Kumar Gautam
> Assignee: Ajay Yadava
> Fix For: 0.7
>
>
> Firing rest request for triage returns a response which looks like:
> {code}
> "vertices": [
> "name: A78e9f5a1-5b8eab89, type: FEED, cluster: A78e9f5a1-9238cc6e, instanceTime: 2010-01-02T00:40Z, tags: [AVAILABLE]"
> ]
> {code}
> The cli output can also be formatted better:
> {code}
> digraph g{
> "name: A78e9f5a1-83173830, type: FEED, cluster: A78e9f5a1-9238cc6e, instanceTime: 2010-01-02T00:40Z, tags: [MISSING]"
> }
> {code}
> Here is the full request/response that was made:
> instance/triage/feed/A78e9f5a1-5b8eab89?start=2010-01-02T00%3A40Z&end=2015-01-05T01%3A00Z&user.name=hrt_qa
> {code}
> {
> "triageGraphs": [
> {
> "vertices": [
> "name: A78e9f5a1-5b8eab89, type: FEED, cluster: A78e9f5a1-9238cc6e, instanceTime: 2010-01-02T00:40Z, tags: [AVAILABLE]"
> ]
> }
> ],
> "requestId": "default/1712257401@qtp-1961945640-622 - 4b19ad04-2433-41c8-ad11-541fc0509e0d\n",
> "message": "default/Success\n",
> "status": "SUCCEEDED"
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)