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

Posted to issues@calcite.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2026/05/09 00:02:00 UTC

[jira] [Updated] (CALCITE-7504) The Hypergraph code does not use lazy logging

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

ASF GitHub Bot updated CALCITE-7504:
------------------------------------
    Labels: pull-request-available  (was: )

> The Hypergraph code does not use lazy logging
> ---------------------------------------------
>
>                 Key: CALCITE-7504
>                 URL: https://issues.apache.org/jira/browse/CALCITE-7504
>             Project: Calcite
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.41.0
>            Reporter: Mihai Budiu
>            Priority: Minor
>              Labels: pull-request-available
>
> The Hypergraph-based join optimization uses logging statements that look like this:
> {code:java}
>        LOGGER.debug("Initialize the dp table. Node {{}} is:\n {}",
>           i,
>           RelOptUtil.toString(hyperGraph.getInput(i)));{code}
> The problem is that these calls will evaluate their arguments, e.g., toString, which can be quite expensive. Ideally a lazy version of logging should be used.



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