[teiid-issues] [JBoss JIRA] (TEIIDSB-170) Automate materialization to JDG

[Ramesh Reddy (Jira)]

    [ https://issues.redhat.com/browse/TEIIDSB-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14091154#comment-14091154 ] 

Ramesh Reddy commented on TEIIDSB-170:
--------------------------------------

>> by reusing the MATERIALIZATION_TARGET property
>This will work actually, this directly represents the cache name. I am ok with this. This is the most simple one.

Actually, this does not work, the scanning we are looking at is done before the maven code-gen is run, so most of the techniques fall into the user's lap to have the knowledge to enter these, thus failing the automation step.


> but yes a full parser of these multiple statements is probably a better way to do this.

I have started looking at yacc passed parser in GO to see if I can write a parser for *only* the DDL statements that we need currently. [~shawkins] can you give examples of inline comments in SQL for these as you mentioned above? Looking through SQL grammar file in Teiid, I find only one place like

{code}
CREATE VIEW {Name} ( columns ...) OPTIONS (...) AS /* comment */ SELECT ...
{code}

I was not sure any others exist?


> 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, 3 days, 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)