[
https://issues.jboss.org/browse/TEIID-2584?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-2584:
-------------------------------------
Yes, startup/shutdown needs to be elevated, we will do that as another issue, as there are
some issues with declaring the DML for them
in vdb.xml and figuring out difference between startup/re-deploy etc.
This is the sample I have been testing with
{code:lang=XML}
<metadata type="DDL"><![CDATA[
CREATE VIEW actor (
actor_id integer,
first_name varchar(45) NOT NULL,
last_name varchar(45) NOT NULL,
last_update timestamp NOT NULL
) OPTIONS (MATERIALIZED 'TRUE', UPDATABLE 'TRUE',
MATERIALIZED_TABLE 'pg.public.mat_actor',
"teiid_rel:MATERIALIZED_STAGE_TABLE"
'pg.public.mat_actor_staging',
"teiid_rel:ALLOW_MATVIEW_MANAGEMENT" 'true',
"teiid_rel:MATVIEW_STATUS_TABLE" 'pg.public.status',
"teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT" 'execute
pg.native(''truncate table mat_actor_staging'');',
"teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT" 'execute
pg.native(''ALTER TABLE mat_actor RENAME TO mat_actor_temp;ALTER TABLE
mat_actor_staging RENAME TO mat_actor;ALTER TABLE mat_actor_temp RENAME TO
mat_actor_staging;'')',
"teiid_rel:MATVIEW_SHARE_SCOPE" 'NONE',
"teiid_rel:MATVIEW_ONERROR_ACTION" 'THROW_EXCEPTION',
"teiid_rel:ON_VDB_DROP_SCRIPT" 'DELETE FROM pg.public.status
WHERE Name=''actor'' AND schemaname = ''sakila''')
AS /*+ cache(ttl:180000)*/SELECT actor_id, first_name, last_name, last_update
from pg."public".actor;
]]>
</metadata>
{code}
Add management features to materialization
------------------------------------------
Key: TEIID-2584
URL:
https://issues.jboss.org/browse/TEIID-2584
Project: Teiid
Issue Type: Feature Request
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Labels: Beta3
Fix For: 8.5
Currently Teiid supports internal and external materialization features. The internal is
managed completely by the Teiid query engine along with the infinispan cache.
External materialization is completely unmanaged and left out to the user to manage it
externally. This goals for this feature are unify the materialization logic for internal
and external, such that both are managed similarly irrespective of the type of
materialization chosen.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira