[jira] [Updated] (HIVE-4631) Hive doesn't flush errors of multi-stage queries to STDERR until end of query

["Brad Ruderman (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HIVE-4631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brad Ruderman updated HIVE-4631:
--------------------------------

    Priority: Major  (was: Minor)
    
> Hive doesn't flush errors of multi-stage queries to STDERR until end of query
> -----------------------------------------------------------------------------
>
>                 Key: HIVE-4631
>                 URL: https://issues.apache.org/jira/browse/HIVE-4631
>             Project: Hive
>          Issue Type: Bug
>          Components: CLI
>    Affects Versions: 0.9.0
>            Reporter: Brad Ruderman
>
> When running a multi-stage query from the CLI for example 
> say the query is:
> SELECT  COUNT(*) FROM ( 
> SELECT user from users
> where datetime = 05-10-2013
> UNION ALL
> SELECT user from users
> where datetime = 05-10-2013 
> ) a
> and the command to execute it:
> hive -e "<query>" 
> If one of the jobs fails for example the 1st of 3, it should immediately write that to the standard error and flush it. Therefore if you are scripting a hive query you can catch the exception and terminate the other jobs rather then having to wait for them to run to handle the exception from the first job.
> See here for more details:
> http://stackoverflow.com/questions/16825066/hive-flush-errors-of-multi-stage-jobs-to-stderr-in-python
> Thanks!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira