[ 
https://issues.apache.org/jira/browse/TRAFODION-3315?focusedWorklogId=271907&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-271907
 ]

ASF GitHub Bot logged work on TRAFODION-3315:
---------------------------------------------

                Author: ASF GitHub Bot
            Created on: 03/Jul/19 22:39
            Start Date: 03/Jul/19 22:39
    Worklog Time Spent: 10m 
      Work Description: Traf-Jenkins commented on issue #1847: [TRAFODION-3315] 
Add Hive exception info to OSIM Hive error message
URL: https://github.com/apache/trafodion/pull/1847#issuecomment-508277962
 
 
   Test Passed.  https://jenkins.esgyn.com/job/Check-PR-master/3240/
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 271907)
    Time Spent: 0.5h  (was: 20m)

> OSIM gives no error detail when Hive failures occur
> ---------------------------------------------------
>
>                 Key: TRAFODION-3315
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-3315
>             Project: Apache Trafodion
>          Issue Type: Improvement
>          Components: sql-cmp
>            Reporter: David Wayne Birdsall
>            Assignee: David Wayne Birdsall
>            Priority: Major
>             Fix For: 2.4
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> OSIM load under the covers uses Hive to load histogram data into the 
> histogram metadata tables.
> When there is a failure at the Hive level, OSIM reports only:
> *** ERROR[6009] The Optimizer Simulator (OSIM): Error running hive SQL.
> This is not at all helpful in diagnosing the problem.
> We should change OSIM so that it also reports the error information returned 
> from Hive.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to