[
https://issues.apache.org/jira/browse/STORM-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15365640#comment-15365640
]
ASF GitHub Bot commented on STORM-1945:
---------------------------------------
Github user harshach commented on the issue:
https://github.com/apache/storm/pull/1541
@HeartSaVioR while we are here can we fix the JSON response as well.
currently what we have is this
[{"spoutLagResult":"[{\"topic\":\"topic\",\"partition\":0,\"consumerCommittedOffset\":1175610,\"logHeadOffset\":5634192,\"lag\":4458582},{\"topic\":\"topic\",\"partition\":1,\"consumerCommittedOffset\":1251325,\"logHeadOffset\":5634192,\"lag\":4382867}]","spoutId":"spout","spoutType":"KAFKA"}]
we should be returning an array instead lets have something like this
{ "spoutId" : "spout"
"spoutType" : "KAFKA"
"spoutLagResult" : [
"topic": // key is topic name
["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},
]
}
> 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)
