[teiid-issues] [JBoss JIRA] (TEIIDSB-170) Automate materialization to JDG
Ramesh Reddy (Jira)
issues at jboss.org
Sun Apr 26 15:52:43 EDT 2020
[ https://issues.redhat.com/browse/TEIIDSB-170?focusedWorklogId=12450895&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-12450895 ]
Ramesh Reddy logged work on TEIIDSB-170:
----------------------------------------
Author: Ramesh Reddy
Created on: 26/Apr/20 3:52 PM
Start Date: 26/Apr/20 3:51 PM
Worklog Time Spent: 3 days
Work Description: Work in the Operator and fixes in the Teiid Spring Boot
Issue Time Tracking
-------------------
Remaining Estimate: 5 hours (was: 3 days, 5 hours)
Time Spent: 4 days, 3 hours (was: 1 day, 3 hours)
Worklog Id: (was: 12450895)
> 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