You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Chunwei Lei (Jira)" <ji...@apache.org> on 2020/06/15 03:42:00 UTC

[jira] [Commented] (CALCITE-4056) Remove Digest from RelNode and RexNode

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

Chunwei Lei commented on CALCITE-4056:
--------------------------------------

The digest of RexNode seems useless, while the digest of RelNode is useful. How can we identify the RelNode if we remove the digest?

> Remove Digest from RelNode and RexNode
> --------------------------------------
>
>                 Key: CALCITE-4056
>                 URL: https://issues.apache.org/jira/browse/CALCITE-4056
>             Project: Calcite
>          Issue Type: Improvement
>          Components: core
>            Reporter: Haisheng Yuan
>            Priority: Major
>
> The digest is used everywhere (RelNode, RexNode, DataType), causing OOM easily for large queries or with complex expressions. Datatype is cached in global interner and can be reused. Unlike RelNode, RexNode is not stored in MEMO as a GROUP, causing it can't be shared. This makes Calcite can't scale for large queries, e.g. CALCITE-3784.



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