[ 
https://issues.apache.org/jira/browse/STORM-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jungtaek Lim resolved STORM-1950.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.1.0
                   2.0.0

Merged by [~sriharsha]

> Change response json of "Topology Lag" REST API to keyed by spoutId, topic, 
> partition
> -------------------------------------------------------------------------------------
>
>                 Key: STORM-1950
>                 URL: https://issues.apache.org/jira/browse/STORM-1950
>             Project: Apache Storm
>          Issue Type: Improvement
>          Components: storm-ui
>    Affects Versions: 1.1.0
>            Reporter: Jungtaek Lim
>            Assignee: Jungtaek Lim
>             Fix For: 2.0.0, 1.1.0
>
>
> From code review for STORM-1945, there's an idea to change JSON response of 
> "Topology Lag" API to keyed by topic, partition number.
> https://github.com/apache/storm/pull/1541#issuecomment-230983140
> I think also make result keyed by spout id would be good.
> Here's sample JSON of output after this issue is resolved.
> {code}
> {
>    "spout1":{
>       "spoutId":"spout1",
>       "spoutType":"KAFKA",
>       "spoutLagResult":{
>          "topic":{
>             "partition0":{
>                "consumerCommittedOffset":1175610,
>                "logHeadOffset":5634192,
>                "lag":4458582
>             },
>             "partition2":{
>                "consumerCommittedOffset":1175610,
>                "logHeadOffset":5634192,
>                "lag":4458582
>             }
>          },
>          "topic2":{
>             "partition0":{
>                "consumerCommittedOffset":1175610,
>                "logHeadOffset":5634192,
>                "lag":4458582
>             },
>             "partition2":{
>                "consumerCommittedOffset":1175610,
>                "logHeadOffset":5634192,
>                "lag":4458582
>             }
>          }
>       }
>    }
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to