[JBoss JIRA] (TEIIDDES-2978) In the materialize wizard, split out the cacheTypeMap
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2978?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2978:
----------------------------------------
This is almost turning into a CP wizard/editor that works with an existing Mat. Model and View?
This would change the pattern/workflow. Almost begs for a separate "configuration" file that's managed outside of Data Tools
> In the materialize wizard, split out the cacheTypeMap
> -----------------------------------------------------
>
> Key: TEIIDDES-2978
> URL: https://issues.jboss.org/browse/TEIIDDES-2978
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Modeling, Usability
> Affects Versions: 10.0.3
> Reporter: Van Halbert
> Priority: Optional
> Fix For: 10.0.3
>
>
> - change the cacheTypeMap to be split out into 3 separate text boxes for the user (cache name, class name, primary key)
> a. the primary key from the view (if it exists) can be use to set the default for the primary key
> b. the class name can be defaulted to what the pojo class to be created
> c. The user then only needs to enter the cache name
> All three must be entered to complete process
> under the covers, the property will be assembled: cacheName + ":" + classname + ":" + primarykey
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (TEIIDDES-2978) In the materialize wizard, split out the cacheTypeMap
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2978?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2978:
-----------------------------------
Fix Version/s: 10.0.3
> In the materialize wizard, split out the cacheTypeMap
> -----------------------------------------------------
>
> Key: TEIIDDES-2978
> URL: https://issues.jboss.org/browse/TEIIDDES-2978
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Modeling, Usability
> Affects Versions: 10.0.3
> Reporter: Van Halbert
> Priority: Optional
> Fix For: 10.0.3
>
>
> - change the cacheTypeMap to be split out into 3 separate text boxes for the user (cache name, class name, primary key)
> a. the primary key from the view (if it exists) can be use to set the default for the primary key
> b. the class name can be defaulted to what the pojo class to be created
> c. The user then only needs to enter the cache name
> All three must be entered to complete process
> under the covers, the property will be assembled: cacheName + ":" + classname + ":" + primarykey
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (TEIIDDES-2982) Missing Table settings in dynamic VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2982?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2982:
----------------------------------------
Tested a bit with this generic model to verify the issues in the description.
Additionally.......
It appears the INDEX constraint in a Column definition is not setting up the EMF Index and it's references correctly. On Generate VDB from vdb.xml it's failing on save:
{code}
Exception in thread "ModelBuffer.Save" java.lang.NullPointerException
at org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getURIFragment(XMLHelperImpl.java:713)
at org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getIDREF(XMLHelperImpl.java:747)
at org.teiid.designer.core.resource.xmi.MtkXmiSaveImpl.saveIDRefMany(MtkXmiSaveImpl.java:320)
at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1370)
at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1224)
at org.teiid.designer.core.resource.xmi.MtkXmiSaveImpl.saveElementID(MtkXmiSaveImpl.java:249)
at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1181)
at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1042)
at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveContainedMany(XMLSaveImpl.java:2417)
at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1553)
at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1224)
at org.teiid.designer.core.resource.xmi.MtkXmiSaveImpl.saveElementID(MtkXmiSaveImpl.java:249)
at org.eclipse.emf.ecore.xmi.impl.XMISaveImpl.writeTopObjects(XMISaveImpl.java:84)
at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.traverse(XMLSaveImpl.java:595)
at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.save(XMLSaveImpl.java:251)
at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doSave(XMLResourceImpl.java:389)
{code}
> Missing Table settings in dynamic VDB
> -------------------------------------
>
> Key: TEIIDDES-2982
> URL: https://issues.jboss.org/browse/TEIIDDES-2982
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs, Import/Export
> Affects Versions: 10.0.2
> Reporter: Mario Majernik
> Fix For: 10.0.3
>
> Attachments: DynamicVDBtesting.zip
>
>
> There are missing Table setiings in dynamic vdb:
> * System(Is System Table checkbox in table dialog) column is always false.(No mention in dynamicVDB)
> * Name In Source and Description is empty in PrimaryKeys tab and Unique Constraint tab.(No mention in dynamic VDB)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (TEIIDDES-2982) Missing Table settings in dynamic VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2982?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2982:
-----------------------------------
Fix Version/s: 10.0.3
> Missing Table settings in dynamic VDB
> -------------------------------------
>
> Key: TEIIDDES-2982
> URL: https://issues.jboss.org/browse/TEIIDDES-2982
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs, Import/Export
> Affects Versions: 10.0.2
> Reporter: Mario Majernik
> Fix For: 10.0.3
>
> Attachments: DynamicVDBtesting.zip
>
>
> There are missing Table setiings in dynamic vdb:
> * System(Is System Table checkbox in table dialog) column is always false.(No mention in dynamicVDB)
> * Name In Source and Description is empty in PrimaryKeys tab and Unique Constraint tab.(No mention in dynamic VDB)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months