[ 
https://issues.apache.org/jira/browse/AMBARI-13279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939387#comment-14939387
 ] 

Nitiraj Singh Rathore commented on AMBARI-13279:
------------------------------------------------

So, the problem is that WebHCat job succeeds even if there was some error in 
pig execution. To see the error user have to open log tab and see what's going 
on (there are exceptions).
My suggestion is 
1) Show logs during the script RUNNING state in live appending, not only in the 
end
2) If results are empty, expand the logs tab (and highlight ERROR lines in 
there)
3) Parse logs for ERROR lines and if there is one, put "warning sign" with help 
text that something possibly went wrong near the COMPLETED label.


> Pig view shows completed but does not state if anything went wrong
> ------------------------------------------------------------------
>
>                 Key: AMBARI-13279
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13279
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-views
>    Affects Versions: 2.1.0
>            Reporter: Nitiraj Singh Rathore
>            Assignee: Nitiraj Singh Rathore
>            Priority: Critical
>             Fix For: 2.1.3
>
>
> Lets say there was some error while executing pig script. In this case the 
> status appears as "Completed" (in green color) and Results is empty and the 
> Log includes the exception that occurred.
> So there is no visual cue to show if there was error and because of it the 
> result set is empty.
> To Reproduce : Include a HCatalog statement in the pig script and run it with 
> the -useHCatalog argument. 
> Example :
> a = LOAD 'someHiveTable' USING org.apache.hive.hcatalog.pig.HCatLoader();
> dump a;
> Executing this without -useHCatalog will create an exception, which will 
> appear in logs but the result will be empty and status will appear as 
> completed. So it is not clear that some exception occurred.



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

Reply via email to