You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Alejandro Fernandez (JIRA)" <ji...@apache.org> on 2014/10/04 04:04:33 UTC
[jira] [Commented] (AMBARI-7643) Jobs view: Input/Output bytes
shows up as 0 for some jobs
[ https://issues.apache.org/jira/browse/AMBARI-7643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158868#comment-14158868 ]
Alejandro Fernandez commented on AMBARI-7643:
---------------------------------------------
Turns out that in Ambari 1.7.0, the Ember javascript library was updated from 1.0-pre to 1.5. In 1.0-pre, attempting to get a field that does not exist would return null, whereas in 1.5 it returns undefined (which cannot be added to another number, hence resulting in dispalying 0 even though hdfsReadBytes had a positive value).
> Jobs view: Input/Output bytes shows up as 0 for some jobs
> ---------------------------------------------------------
>
> Key: AMBARI-7643
> URL: https://issues.apache.org/jira/browse/AMBARI-7643
> Project: Ambari
> Issue Type: Bug
> Components: contrib
> Affects Versions: 1.7.0
> Reporter: Alejandro Fernandez
> Assignee: Alejandro Fernandez
> Fix For: 1.7.0
>
>
> The same job query shows correct # of bytes in 1.6.1 built-in jobs tab (see attached screenshot), whereas it shows 0 bytes in 1.7.0 jobs view.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)