[
https://issues.jboss.org/browse/TEIIDDES-3095?page=com.atlassian.jira.plu...
]
Van Halbert commented on TEIIDDES-3095:
---------------------------------------
In the current designer, you select "Materialize", it walks you thru a wizard:
1. (1st panel) Enter the name of the new Source Model to put the new matview and staging
source tables.
2 (2nd panel) select option to generate pojo
results: create 2 source tables, where the staging table has an extension property
(Primary table) to indicates which source table is the matview source.
To support JDG 7.1, there is a different set of extension properties that apply (the JDG
6.x properties are not used), example: "infinispan-hotrod":"CACHE", is
the important one.
What do we need changed:
- on the 1st panel, enable the user to select which JDG they are using: JDG 7.1 or JDG
6.6
- based on selection do the following:
JDG 6.6 - set namespace to "infinispan"
JDG 7.1 - set namespace to "infinispan-hotrod"
if JDG 6.6 is selected, enable "NEXT" and "FINISH" - do as it does
now
if JDG 7.1 is selected, enable only "FINISH" (don't need to create pojo).
The wizard curently creates both tables (matview and staging), and that should remain the
same.
When view is selected to be materialized, can the user choose which
extension properties to use
-----------------------------------------------------------------------------------------------
Key: TEIIDDES-3095
URL:
https://issues.jboss.org/browse/TEIIDDES-3095
Project: Teiid Designer
Issue Type: Enhancement
Components: Modeling
Affects Versions: 11.1
Reporter: Van Halbert
Assignee: Barry LaFond
Fix For: 11.0.2
With the support of the new infinispan-hotrod (JDG 7.1) translator that will be used,
there is a different extension properties to be used. And when the user selects a view
to be materialized, can an option be added to the first panel (which shows the source and
target models) that allows the user to select which extension properties to use? And if
they choose the option for JDG 7.1, then no need to goto next panel (create pojo).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)