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

[Jan Stastny (JIRA)]

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

Jan Stastny updated TEIID-3215:
-------------------------------
    Attachment: mat-views-vdb.xml


The attached vdb should demonstrate the issue. Below are schemas of required tables.

CREATE TABLE check_table(
id VARCHAR(50) PRIMARY KEY,
vdb_create INT DEFAULT 0,
vdb_drop INT DEFAULT 0,
before_load INT DEFAULT 0,
after_load INT DEFAULT 0
)
CREATE TABLE IF NOT EXISTS status(VDBName varchar(50) not null, VDBVersion integer not null, SchemaName varchar(50) not null, Name varchar(256) not null, TargetSchemaName varchar(50), TargetName varchar(256) not null, Valid boolean not null, LoadState varchar(25) not null, Cardinality long, Updated timestamp not null, LoadNumber long not null, PRIMARY KEY (VDBName, VDBVersion, SchemaName, Name));

CREATE TABLE IF NOT EXISTS mat_view(customer_id INT NOT NULL,total_amount INT);ALTER TABLE mat_view ADD CONSTRAINT pk_customer_id PRIMARY KEY (customer_id);

CREATE TABLE IF NOT EXISTS mat_view_stage(customer_id INT NOT NULL,total_amount INT);ALTER TABLE mat_view_stage ADD CONSTRAINT pk_customer_stage_id PRIMARY KEY (customer_id);

> 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
>              Labels: Final
>             Fix For: 8.7.1, 8.9
>
>         Attachments: mat-views-vdb.xml
>
>
> 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,...)



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