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

Tim Armstrong commented on IMPALA-8849:
---------------------------------------

Reverting this commit fixed the issue for me

commit c2516d220da8e532b6ebdb6f3a12e7ad97c4f597
Author: Csaba Ringhofer <[email protected]>
Date:   Wed Apr 17 15:01:07 2019 +0200

    IMPALA-8409: Fix row-size for STRING columns with unknown stats
    
    Explain returned row-size=11B for STRING columns without statistics.
    The issue was caused by adding -1 (meaning unknown) to the 12 byte
    slot size (sizeof(StringValue)). The code in TupleDescriptor.java
    tried to handle this by checking if the size is -1, but it was
    already 11 at this point.
    
    There is more potential for cleanup, but I wanted to keep this
    change minimal.
    
    Testing:
    - revived some tests in CatalogTest.java that were removed
      in 2013 due to flakiness
    - added an EE test that checks row size with and without stats
    - fixed a similar test, test_explain_validate_cardinality_estimates
      (the format of the line it looks for has changed, which lead to
      skipping the actual verification and accepting everything)
    - ran core FE and EE tests
    
    Change-Id: I866acf10b2c011a735dee019f4bc29358f2ec4e5
    Reviewed-on: http://gerrit.cloudera.org:8080/13190
    Reviewed-by: Impala Public Jenkins <[email protected]>
    Tested-by: Impala Public Jenkins <[email protected]>


> IllegalStateException in HashJoinNode because of missing memory estimate
> ------------------------------------------------------------------------
>
>                 Key: IMPALA-8849
>                 URL: https://issues.apache.org/jira/browse/IMPALA-8849
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Frontend
>    Affects Versions: Impala 3.3.0
>            Reporter: Tim Armstrong
>            Assignee: Tim Armstrong
>            Priority: Blocker
>         Attachments: query4.sql
>
>
> [~grahn] reports the below error when running the attached TPC-DS query on 
> uncompressed text with stats.
> {noformat}
> I0808 03:27:16.621085 150090 jni-util.cc:288] 
> 8945e9f76f33dca0:8bf31c4700000000] java.lang.IllegalStateException: Mem 
> estimate must be set
>     at com.google.common.base.Preconditions.checkState(Preconditions.java:149)
>     at 
> org.apache.impala.planner.ResourceProfileBuilder.build(ResourceProfileBuilder.java:73)
>     at 
> org.apache.impala.planner.HashJoinNode.computeNodeResourceProfile(HashJoinNode.java:252)
>     at 
> org.apache.impala.planner.PlanFragment.computeResourceProfile(PlanFragment.java:238)
>     at org.apache.impala.planner.Planner.computeResourceReqs(Planner.java:416)
>     at 
> org.apache.impala.service.Frontend.createExecRequest(Frontend.java:1162)
>     at 
> org.apache.impala.service.Frontend.getPlannedExecRequest(Frontend.java:1477)
>     at 
> org.apache.impala.service.Frontend.doCreateExecRequest(Frontend.java:1341)
>     at org.apache.impala.service.Frontend.getTExecRequest(Frontend.java:1236)
>     at 
> org.apache.impala.service.Frontend.createExecRequest(Frontend.java:1206)
>     at 
> org.apache.impala.service.JniFrontend.createExecRequest(JniFrontend.java:154)
> I0808 03:27:16.621861 150090 status.cc:124] 
> 8945e9f76f33dca0:8bf31c4700000000] IllegalStateException: Mem estimate must 
> be set
>     @           0xb9af99
>     @          0x11f785e
>     @          0x10ab9a3
>     @          0x10d0f54
>     @          0x10e2a2c
>     @          0x1125f8d
>     @          0x1458c54
>     @          0x145810c
>     @           0xb68769
>     @           0xf91ca0
>     @           0xf8791e
>     @           0xf887b1
>     @          0x127cd2f
>     @          0x127d8d9
>     @          0x1ac0709
>     @     0x7f11ea4d7dd4
>     @     0x7f11e6f1e02c
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

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

Reply via email to