[teiid-issues] [JBoss JIRA] (TEIIDSB-170) Automate materialization to JDG
Ramesh Reddy (Jira)
issues at jboss.org
Wed Apr 29 16:07:12 EDT 2020
[ https://issues.redhat.com/browse/TEIIDSB-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14066695#comment-14066695 ]
Ramesh Reddy commented on TEIIDSB-170:
--------------------------------------
Where caches in Infinispan can be managed as Custom Resources. Teiid would need this to manage caches when working with shared clusters
https://github.com/infinispan/infinispan-operator/issues/356
Using a REST API https://infinispan.org/docs/dev/titles/rest/rest.html#rest_v2_remove_cache
However, in Openshift there is no route created to reach the HTTP endpoint
> 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: 4 days, 3 hours
> Remaining Estimate: 5 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)
More information about the teiid-issues
mailing list