[
https://issues.apache.org/jira/browse/CALCITE-4551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17308953#comment-17308953
]
Julian Hyde commented on CALCITE-4551:
--------------------------------------
Are these changes in commit
[28f313c|https://github.com/apache/calcite/pull/2378/commits/28f313c97e60afe8fa33f5e06156918f4bc351b9]?
When you say FlattenList do you mean FlatList?
I think you are saying that because a metadata call has no arguments (other
than the metadata type and the RelNode) the key is always the same, and your
optimization works for those types of metadata. Is that right?
> Fly Weight for MD Cache Keys
> ----------------------------
>
> Key: CALCITE-4551
> URL: https://issues.apache.org/jira/browse/CALCITE-4551
> Project: Calcite
> Issue Type: Improvement
> Reporter: James Starr
> Priority: Major
> Labels: pull-request-available
>
> Create cache keys for metadata calls generates a fair bit of object turn in
> trivial cases, more expensive than the actual metadata call. Many metadata
> calls could reuse their cache keys since the are functionally identical.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
