[
https://issues.apache.org/jira/browse/IMPALA-8464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16834301#comment-16834301
]
Tim Armstrong commented on IMPALA-8464:
---------------------------------------
I figured out what was going on - the test was actually exercising the
behaviour of IMPALA-7587 where the column comments are only returned if the
table is loaded. The local catalog fixes this weirdness. So I just need to
update the test to reflect the new, more sane, behaviour for the local catalog.
> JdbcTest.testMetaDataGetColumnComments() fails with local catalog
> -----------------------------------------------------------------
>
> Key: IMPALA-8464
> URL: https://issues.apache.org/jira/browse/IMPALA-8464
> Project: IMPALA
> Issue Type: Bug
> Components: Catalog
> Affects Versions: Impala 3.1.0, Impala 3.2.0
> Reporter: Tim Armstrong
> Assignee: Tim Armstrong
> Priority: Major
>
> {noformat}
> Error Message
> Incorrect table comment expected:<[]> but was:<[table comment]>
> Stacktrace
> org.junit.ComparisonFailure: Incorrect table comment expected:<[]> but
> was:<[table comment]>
> at org.junit.Assert.assertEquals(Assert.java:115)
> at
> org.apache.impala.service.JdbcTest.testMetaDataGetColumnComments(JdbcTest.java:484)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
> at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:386)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:323)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:143)
> Standard Output
> 19/04/26 18:35:36 INFO testutil.ImpalaJdbcClient: Using JDBC Driver Name:
> org.apache.hive.jdbc.HiveDriver
> 19/04/26 18:35:36 INFO testutil.ImpalaJdbcClient: Connecting to:
> jdbc:hive2://localhost:21050/default;auth=noSasl
> 19/04/26 18:35:36 INFO jdbc.Utils: Supplied authorities: localhost:21050
> 19/04/26 18:35:36 INFO jdbc.Utils: Resolved authority: localhost:21050
> 19/04/26 18:35:36 INFO testutil.ImpalaJdbcClient: Using JDBC Driver Name:
> org.apache.hive.jdbc.HiveDriver
> 19/04/26 18:35:36 INFO testutil.ImpalaJdbcClient: Connecting to:
> jdbc:hive2://localhost:21050/default;auth=noSasl
> 19/04/26 18:35:36 INFO jdbc.Utils: Supplied authorities: localhost:21050
> 19/04/26 18:35:36 INFO jdbc.Utils: Resolved authority: localhost:21050
> 19/04/26 18:35:36 INFO testutil.ImpalaJdbcClient: Using JDBC Driver Name:
> org.apache.hive.jdbc.HiveDriver
> 19/04/26 18:35:36 INFO testutil.ImpalaJdbcClient: Connecting to:
> jdbc:hive2://localhost:21050/default;auth=noSasl
> 19/04/26 18:35:36 INFO jdbc.Utils: Supplied authorities: localhost:21050
> 19/04/26 18:35:36 INFO jdbc.Utils: Resolved authority: localhost:21050
> 19/04/26 18:35:36 INFO testutil.ImpalaJdbcClient: Using JDBC Driver Name:
> org.apache.hive.jdbc.HiveDriver
> 19/04/26 18:35:36 INFO testutil.ImpalaJdbcClient: Connecting to:
> jdbc:hive2://localhost:21050/default;auth=noSasl
> 19/04/26 18:35:36 INFO jdbc.Utils: Supplied authorities: localhost:21050
> 19/04/26 18:35:36 INFO jdbc.Utils: Resolved authority: localhost:21050
> 19/04/26 18:36:01 INFO service.FeSupport: Loading libfesupport.so
> 19/04/26 18:36:01 INFO service.FeSupport: Loaded libfesupport.so
> 19/04/26 18:36:01 INFO util.JvmPauseMonitor: Starting JVM pause monitor
> {noformat}
> Not sure what is going wrong here.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
