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

Fang-Yu Rao commented on IMPALA-1995:
-------------------------------------

We have seen a similar failure recently.
{code:java}
Error Message
section SCANRANGELOCATIONS of query:
select * from functional_hbase.stringids
where id < '5'
and tinyint_col = 5
Actual does not match expected result:
  HBASE KEYRANGE 1:3
^^^^^^^^^^^^^^^^^^^^
  HBASE KEYRANGE 3:5
  HBASE KEYRANGE <unbounded>:1
NODE 0:

Expected:
  HBASE KEYRANGE 3:5
  HBASE KEYRANGE <unbounded>:3
NODE 0:
Stacktrace
java.lang.AssertionError: 
section SCANRANGELOCATIONS of query:
select * from functional_hbase.stringids
where id < '5'
and tinyint_col = 5
Actual does not match expected result:
  HBASE KEYRANGE 1:3
^^^^^^^^^^^^^^^^^^^^
  HBASE KEYRANGE 3:5
  HBASE KEYRANGE <unbounded>:1
NODE 0:

Expected:
  HBASE KEYRANGE 3:5
  HBASE KEYRANGE <unbounded>:3
NODE 0:

        at org.junit.Assert.fail(Assert.java:88)
        at 
org.apache.impala.planner.PlannerTestBase.runPlannerTestFile(PlannerTestBase.java:924)
        at 
org.apache.impala.planner.PlannerTestBase.runPlannerTestFile(PlannerTestBase.java:839)
        at 
org.apache.impala.planner.PlannerTest.testHbaseNoKeyEstimate(PlannerTest.java:211)
        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.RunBefores.evaluate(RunBefores.java:26)
        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)
{code}


> Flaky test: PlannerTest.testHbase: splits for HBASE KEYRANGE not set up 
> correctly.
> ----------------------------------------------------------------------------------
>
>                 Key: IMPALA-1995
>                 URL: https://issues.apache.org/jira/browse/IMPALA-1995
>             Project: IMPALA
>          Issue Type: Task
>          Components: Frontend
>    Affects Versions: Impala 2.3.0, Impala 3.2.0
>            Reporter: Alexander Behm
>            Assignee: Joe McDonnell
>            Priority: Critical
>              Labels: broken-build, flaky, test-infra
>             Fix For: Impala 2.13.0, Impala 3.1.0
>
>
> Looks like testdata/bin/split-hbase.sh does not always set up the ranges in 
> the way we want. See failure below.
> Example run:
> http://sandbox.jenkins.cloudera.com/job/impala-master-cdh5-trunk/1090/
> {code}
> Stack Trace:
> java.lang.AssertionError: section SCANRANGELOCATIONS of query:
> select * from functional_hbase.alltypessmall
> where id < 5
> actual result doesn't match expected result:
>   HBASE KEYRANGE port=16202 3:7
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>   HBASE KEYRANGE port=16203 7:<unbounded>
>   HBASE KEYRANGE port=16203 <unbounded>:3
> NODE 0:
> expected:
>   HBASE KEYRANGE port=16201 <unbounded>:3
>   HBASE KEYRANGE port=16202 3:7
>   HBASE KEYRANGE port=16203 7:<unbounded>
> NODE 0:
> section SCANRANGELOCATIONS of query:
> select * from functional_hbase.stringids
> where id < '5'
> and tinyint_col = 5
> actual result doesn't match expected result:
>   HBASE KEYRANGE port=16201 1:3
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>   HBASE KEYRANGE port=16202 3:5
>   HBASE KEYRANGE port=16203 <unbounded>:1
> NODE 0:
> expected:
>   HBASE KEYRANGE port=16201 <unbounded>:3
>   HBASE KEYRANGE port=16202 3:5
> NODE 0:
> section SCANRANGELOCATIONS of query:
> select * from functional_hbase.alltypesagg
> where bigint_col is not null and bool_col = true
> actual result doesn't match expected result:
>   HBASE KEYRANGE port=16201 1:3
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>   HBASE KEYRANGE port=16202 3:7
>   HBASE KEYRANGE port=16203 7:<unbounded>
>   HBASE KEYRANGE port=16203 <unbounded>:1
> NODE 0:
> expected:
>   HBASE KEYRANGE port=16201 <unbounded>:3
>   HBASE KEYRANGE port=16202 3:7
>   HBASE KEYRANGE port=16203 7:<unbounded>
> NODE 0:
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to