[
https://issues.apache.org/jira/browse/TRAFODION-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hans Zeller resolved TRAFODION-2723.
------------------------------------
Resolution: Not A Problem
After debugging I realized that there is already code in
ControlDB::setControlDefault() that flushes the entire NATable cache when we
set this CQD, so no additional work is required.
> Add check to NATable cache for snapshot info
> --------------------------------------------
>
> Key: TRAFODION-2723
> URL: https://issues.apache.org/jira/browse/TRAFODION-2723
> Project: Apache Trafodion
> Issue Type: Sub-task
> Components: sql-cmp
> Affects Versions: 2.2-incubating
> Environment: any, using snapshot scans
> Reporter: Hans Zeller
> Assignee: Hans Zeller
> Fix For: 2.2-incubating
>
>
> TRAFODION-2716 added code to read snapshot info conditionally. This means
> that most NATable cache entries will not have this information. Now, if a
> user turns on snapshot scan after accessing some tables, the cache entries
> will prevent snapshot scans from happening, or they may create unnecessary
> snapshots.
> Like it is done for other CQDs that influence NATable cache entries, we need
> to invalidate the cache if the TRAF_TABLE_SNAPSHOT_SCAN has gone from NONE to
> some value other than NONE. There is no need to check in the other direction,
> extra snapshot scan info won't hurt.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
