[
https://issues.apache.org/jira/browse/STORM-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15365698#comment-15365698
]
ASF GitHub Bot commented on STORM-1945:
---------------------------------------
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1541
@harshach
I guess you mean this:
```
[
{
"spoutId":"spout",
"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
}
}
}
}
]
```
I agree this is better for removing duplicated thing and also easy to find
by path. I'll update it.
> Internal Server Error shown on topology page for topology using KafkaSpout
> --------------------------------------------------------------------------
>
> Key: STORM-1945
> URL: https://issues.apache.org/jira/browse/STORM-1945
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-ui
> Affects Versions: 2.0.0, 1.1.0
> Reporter: Jungtaek Lim
> Assignee: Jungtaek Lim
> Priority: Critical
> Attachments: Screen Shot 2016-07-06 at 4.25.41 PM.png
>
>
> When opening topology page which uses old storm-kafka Spout, page shows
> Internal Server Error on bottom side.
> And REST API /api/v1/topology/:topology/lag also shows Internal Server Error.
> Its errorMessage is describing NPE, but stack track gives less help since
> it's already within catch statement so we can't trace why origin exception is
> thrown by only looking at errorMessage. And there's no error message on ui
> log file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
