[
https://issues.apache.org/jira/browse/CALCITE-3149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17085065#comment-17085065
]
Jesus Camacho Rodriguez commented on CALCITE-3149:
--------------------------------------------------
However, those types should not be evicted from the cache since it uses by
default strong keys, and the values should not be garbage collected while in
use since they will be strongly referenced? The code is complex (especially
because of this duality with the cache and the interner... do we really need
both?), that is why I asked the question, but I did not have the chance to look
in detail. If there is a regression/bug, I think we should understand clearly
why it is happening and come up with an alternative before just reverting the
change.
> CACHE in RelDataTypeFactoryImpl can't be garbage collected
> -----------------------------------------------------------
>
> Key: CALCITE-3149
> URL: https://issues.apache.org/jira/browse/CALCITE-3149
> Project: Calcite
> Issue Type: Bug
> Components: core
> Reporter: Haisheng Yuan
> Assignee: Haisheng Yuan
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.21.0
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> Key and Value are pointing to the same object, even with soft value
> references, the objects in CACHE will not be garbage collected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
