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

Ashutosh Chauhan commented on HCATALOG-544:
-------------------------------------------

+1
                
> HCatSemanticAnalyzer should log the unsupported token in its error message
> --------------------------------------------------------------------------
>
>                 Key: HCATALOG-544
>                 URL: https://issues.apache.org/jira/browse/HCATALOG-544
>             Project: HCatalog
>          Issue Type: Bug
>            Reporter: Travis Crawford
>            Assignee: Travis Crawford
>         Attachments: HCATALOG-544_log_token.1.patch
>
>
> The [HCatalog trunk 
> build|https://builds.apache.org/job/Hcatalog-trunk-build/] is currently 
> failing on CI in a way that I cannot reproduce locally. Its failing when 
> attempting to run an unsupported operation through the HCat CLI.
> This change simply logs the type of operation that failed, with hopes it 
> helps us understand why the build is failing.
> {code}
> 12/11/02 03:15:41 ERROR ql.Driver: FAILED: SemanticException Operation not 
> supported.
> org.apache.hadoop.hive.ql.parse.SemanticException: Operation not supported.
>       at 
> org.apache.hcatalog.cli.SemanticAnalysis.HCatSemanticAnalyzer.preAnalyze(HCatSemanticAnalyzer.java:150)
>       at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:429)
>       at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:335)
>       at org.apache.hadoop.hive.ql.Driver.run(Driver.java:903)
>       at org.apache.hcatalog.cli.HCatDriver.run(HCatDriver.java:42)
>       at 
> org.apache.hcatalog.hbase.TestHBaseBulkOutputFormat.bulkModeHCatOutputFormatTest(TestHBaseBulkOutputFormat.java:362)
>       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>       at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>       at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>       at java.lang.reflect.Method.invoke(Method.java:597)
>       at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
>       at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>       at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
>       at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
>       at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
>       at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
>       at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
>       at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
>       at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
>       at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
>       at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
>       at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
>       at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
>       at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
>       at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
>       at junit.framework.JUnit4TestAdapter.run(JUnit4TestAdapter.java:39)
>       at 
> org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:518)
>       at 
> org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1052)
>       at 
> org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:906)
> {code}

--
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

Reply via email to