[
https://issues.apache.org/jira/browse/CALCITE-7504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stamatis Zampetakis updated CALCITE-7504:
-----------------------------------------
Summary: Use lazy logging in Hypergraph code (was: The Hypergraph code
does not use lazy logging)
> Use lazy logging in Hypergraph code
> -----------------------------------
>
> 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
> Assignee: Mihai Budiu
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.42.0
>
>
> 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)
