phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maryann Xue (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (PHOENIX-3341) Schema update is not visible to following statements of the same connection due to CalciteSchema caching.
Date Thu, 03 Aug 2017 19:18:00 GMT

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

Maryann Xue resolved PHOENIX-3341.
----------------------------------
    Resolution: Fixed

> Schema update is not visible to following statements of the same connection due to CalciteSchema
caching.
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-3341
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3341
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Maryann Xue
>            Assignee: Maryann Xue
>              Labels: calcite
>
> The TableRef object contains a timestamp which will be used for TableScan. The timestamp
should be set at the time of the statement being compiled. Now that the table resolving goes
from Calcite and CalciteSchema caches TableEntry through the whole connection, the table will
not be re-resolved if any previous statement has already resolved it. If a previous statement
did an update, the next statement cannot see the update since it's holding a TableRef object
containing the old timestamp.
> The CalciteSchema caching would also be a problem if a table, a view, or a function is
modified or dropped.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message