[teiid-issues] [JBoss JIRA] (TEIID-3215) External Materialization ON_VDB_START_SCRIPT invocation issues

[Ramesh Reddy (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ramesh Reddy updated TEIID-3215:
--------------------------------
             Fix Version/s: 8.7.1
                            8.9
                    Tester: Jan Stastny
                  Assignee: Ramesh Reddy  (was: Steven Hawkins)
    Workaround Description: Only deploy the VDB to the running server, not copy to the directory and start the server
                Workaround: Workaround Exists
      Estimated Difficulty: Low
               Component/s: Server
                   Affects: Documentation (Ref Guide, User Guide, etc.)


> External Materialization ON_VDB_START_SCRIPT invocation issues
> --------------------------------------------------------------
>
>                 Key: TEIID-3215
>                 URL: https://issues.jboss.org/browse/TEIID-3215
>             Project: Teiid
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 8.7
>            Reporter: Jan Stastny
>            Assignee: Ramesh Reddy
>             Fix For: 8.7.1, 8.9
>
>
> With materialized view I have set teiid_rel:ON_VDB_START_SCRIPT property for the external matview table. (Simple query to increment a column in table to count invocations.) 
> Invocation of the script is dependent upon the way the vdb is deployed. The first case (A) doesn't invoke the script, the second (B) does.
> A - 1. Copy the vdbname-vdb.xml into deployments folder
>       2. Start the server
> B - 1. Start the server
>       2. Copy the vdbname-vdb.xml into deployments folder
> That means that after server stop (maintenance) the script is not invoked on start, which can cause problems when the script is used to initialize running environment (clear table, create temporary table natively,...)



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)