You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Namit Jain (JIRA)" <ji...@apache.org> on 2010/12/10 20:11:02 UTC

[jira] Created: (HIVE-1847) option of continue on error

option of continue on error
---------------------------

                 Key: HIVE-1847
                 URL: https://issues.apache.org/jira/browse/HIVE-1847
             Project: Hive
          Issue Type: Improvement
            Reporter: Namit Jain


In "hive -f <script>", if any sql/command fails in that script than hive exists with exit status -1, without continuing the remaining hive commands.
Sometimes it is better to continue the script even during errors. 
For example, if a hive sql script contains many drop table commands, the command would exit when it could not find a table. But in this case, it is preferable to continue dropping remaining tables

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (HIVE-1847) option of continue on error

Posted by "Namit Jain (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HIVE-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Namit Jain resolved HIVE-1847.
------------------------------

    Resolution: Not A Problem

Thanks Thiruvel

> option of continue on error
> ---------------------------
>
>                 Key: HIVE-1847
>                 URL: https://issues.apache.org/jira/browse/HIVE-1847
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Namit Jain
>
> In "hive -f <script>", if any sql/command fails in that script than hive exists with exit status -1, without continuing the remaining hive commands.
> Sometimes it is better to continue the script even during errors. 
> For example, if a hive sql script contains many drop table commands, the command would exit when it could not find a table. But in this case, it is preferable to continue dropping remaining tables

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (HIVE-1847) option of continue on error

Posted by "Thiruvel Thirumoolan (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HIVE-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973652#action_12973652 ] 

Thiruvel Thirumoolan commented on HIVE-1847:
--------------------------------------------

hive.cli.errors.ignore?

Its set to 'false' by default and after setting it to 'true', all commands in the script are executed, no matter how many failed.

> option of continue on error
> ---------------------------
>
>                 Key: HIVE-1847
>                 URL: https://issues.apache.org/jira/browse/HIVE-1847
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Namit Jain
>
> In "hive -f <script>", if any sql/command fails in that script than hive exists with exit status -1, without continuing the remaining hive commands.
> Sometimes it is better to continue the script even during errors. 
> For example, if a hive sql script contains many drop table commands, the command would exit when it could not find a table. But in this case, it is preferable to continue dropping remaining tables

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (HIVE-1847) option of continue on error

Posted by "Namit Jain (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HIVE-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974544#action_12974544 ] 

Namit Jain commented on HIVE-1847:
----------------------------------

That sounds like a good idea

> option of continue on error
> ---------------------------
>
>                 Key: HIVE-1847
>                 URL: https://issues.apache.org/jira/browse/HIVE-1847
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Namit Jain
>
> In "hive -f <script>", if any sql/command fails in that script than hive exists with exit status -1, without continuing the remaining hive commands.
> Sometimes it is better to continue the script even during errors. 
> For example, if a hive sql script contains many drop table commands, the command would exit when it could not find a table. But in this case, it is preferable to continue dropping remaining tables

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (HIVE-1847) option of continue on error

Posted by "Namit Jain (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HIVE-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974545#action_12974545 ] 

Namit Jain commented on HIVE-1847:
----------------------------------

@Thiruvel, please assign it to yourself if you are planning to work on it

> option of continue on error
> ---------------------------
>
>                 Key: HIVE-1847
>                 URL: https://issues.apache.org/jira/browse/HIVE-1847
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Namit Jain
>
> In "hive -f <script>", if any sql/command fails in that script than hive exists with exit status -1, without continuing the remaining hive commands.
> Sometimes it is better to continue the script even during errors. 
> For example, if a hive sql script contains many drop table commands, the command would exit when it could not find a table. But in this case, it is preferable to continue dropping remaining tables

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (HIVE-1847) option of continue on error

Posted by "Thiruvel Thirumoolan (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HIVE-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974603#action_12974603 ] 

Thiruvel Thirumoolan commented on HIVE-1847:
--------------------------------------------

@Namit, i wasn't clear.

The param "hive.cli.errors.ignore" already exists and does what I mentioned above. Could not find any related JIRA other than source code (HiveConf.java).

--
$ cat test_error.q 
drop table does_not_exist;
create table incomplete_syntax(a, string, );
create table invites(foo int, bar string);

$ hive -hiveconf hive.cli.errors.ignore=true -f test_error.q 
OK
Time taken: 0.573 seconds
FAILED: Parse Error: line 2:32 cannot recognize input ',' in column type

OK
Time taken: 3.143 seconds
---

Would u like anything else to be covered as part of this JIRA?

> option of continue on error
> ---------------------------
>
>                 Key: HIVE-1847
>                 URL: https://issues.apache.org/jira/browse/HIVE-1847
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Namit Jain
>
> In "hive -f <script>", if any sql/command fails in that script than hive exists with exit status -1, without continuing the remaining hive commands.
> Sometimes it is better to continue the script even during errors. 
> For example, if a hive sql script contains many drop table commands, the command would exit when it could not find a table. But in this case, it is preferable to continue dropping remaining tables

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.