[STORM-1057] Add throughput metrics to spouts/bolts and display them on web ui for 1.x-branch

[wangli1426]

Hi @HeartSaVioR, @revans2, @harshach,@d2r,@unsleepy22,

I upmerge PR #753 to 1.x-branch.
Sorry for the delay.
Please review.

Thanks.

[wangli1426]

@HeartSaVioR Can you review this PR? Thanks.

[HeartSaVioR]

@wangli1426
Sorry I haven't had time to review this right now. I'll take a look when I get time.
Btw, since you're modifying ported clojure files, you need to port your change to master as well. If you don't want to address both Clojure and Java, addressing master is higher priority.

[wangli1426]

Can I create a new PR based on the latest master version rather than upmerging this RP to master? The former would be much easier, since a lot of changes have been made from 1.x to 2.x.

Sent from my iPhone

On 28 Sep 2016, at 8:02 AM, Jungtaek Lim notifications@github.com wrote:

@wangli1426
Sorry I haven't had time to review this right now. I'll take a look when I get time.
Btw, since you're modifying ported clojure files, you need to port your change to master as well. If you don't want to address both Clojure and Java, addressing master is higher priority.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[HeartSaVioR]

Yes sure. You don't essentially need to upmerge/rebase old pull request if you want to provide new pull request based on current.

[wangli1426]

Thanks for the prompt response. I will create a new pull request for master asap.

Sent from my iPhone

On 28 Sep 2016, at 9:09 AM, Jungtaek Lim notifications@github.com wrote:

Yes sure. You don't essentially need to upmerge/rebase old pull request if you want to provide new pull request based on current.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.