[
https://issues.redhat.com/browse/TEIIDSB-170?page=com.atlassian.jira.plug...
]
Ramesh Reddy commented on TEIIDSB-170:
--------------------------------------
Looks like we can not add this in the vdb-codegen-plugin at all, if we handle the
modification there is no way inject the modified DDL back into Teiid VDB. In the Operator
model, the VDB is already written to disk (image). This needs to be handled in the Teiid
Spring Boot engine in boot sequence before deployment of the vdb.
Automate materialization to JDG
-------------------------------
Key: TEIIDSB-170
URL:
https://issues.redhat.com/browse/TEIIDSB-170
Project: Teiid Spring Boot
Issue Type: Enhancement
Components: OpenShift
Reporter: Steven Hawkins
Assignee: Ramesh Reddy
Priority: Major
Fix For: 1.5.0
Original Estimate: 1 week
Time Spent: 1 hour
Remaining Estimate: 4 days, 7 hours
Create an internal materialization replacement needs that is turnkey materialization to
JDG (little to no user setup required)
- the operator may create the infinispan cluster if needed
- the status table and internal representation of the materialization target would be
setup automatically
For the user this would be as simple marking a view as materialized and then it would be
populated in jdg upon deployment. They would not have any concerns with cache naming,
status tables, etc.
For simplicity the initial version would make a similar assumption to the current
internal logic - it is for only a specific vdb. If the vdb cr is modified, then it's
expected that the cache would be recreated.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)