[
https://issues.redhat.com/browse/TEIIDSB-170?page=com.atlassian.jira.plug...
]
Ramesh Reddy edited comment on TEIIDSB-170 at 5/1/20 6:27 PM:
--------------------------------------------------------------
Will be adding the following environment properties to the Pod from the Operator
- TEIID_NODENAME - OpenShift Node Name where the Pod exists
- TEIID_PODNAME - Pod Name
- TEIID_LABELS - Labels set on the CR
The Materialization tables will be added with a random name in them, so that there will be
no collisions in rollup deployments of VDBs
was (Author: rareddy):
Will be adding the following environment properties to the Pod from the Operator
- TEIID_NODENAME - OpenShift Node Name where the Pod exists
- TEIID_PODIP - Pod IP
- TEIID_LABELS - Labels set on the CR
The Materialization tables will be added with a random name in them, so that there will be
no collisions in rollup deployments of VDBs
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 week, 1 day, 2 hours
Remaining Estimate: 0 minutes
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)