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

Posted to issues@flink.apache.org by "Sergey Nuyanzin (Jira)" <ji...@apache.org> on 2024/09/25 07:59:00 UTC

[jira] [Resolved] (FLINK-36361) Do not use StringBuilder for EquivalentExprShuttle

     [ https://issues.apache.org/jira/browse/FLINK-36361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergey Nuyanzin resolved FLINK-36361.
-------------------------------------
    Fix Version/s: 2.0-preview
       Resolution: Fixed

> Do not use StringBuilder for EquivalentExprShuttle
> --------------------------------------------------
>
>                 Key: FLINK-36361
>                 URL: https://issues.apache.org/jira/browse/FLINK-36361
>             Project: Flink
>          Issue Type: Bug
>          Components: Table SQL / Planner
>            Reporter: Sergey Nuyanzin
>            Assignee: Sergey Nuyanzin
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.0-preview
>
>
> Currently there is {{EquivalentExprShuttle}} where there is a map of {{toString}} node to {{RelNode}}. In fact there is no need for toString which is calculated each time with usage of {{StringBuilder}} under the hood. And even more we faced one weird case where it consumes memory.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)